Overview Review Traffic Revenue SEO
Hosting Registration Security Technical Related

wondermomwannabe.com

wondermomwannabe.com is SSL secured

Free website and domain report on wondermomwannabe.com

Last Updated: 10th November, 2021 Update Now
Overview

Snoop Summary for wondermomwannabe.com

This is a free and comprehensive report about wondermomwannabe.com. The domain wondermomwannabe.com is currently hosted on a server located in Phoenix, Arizona in United States with the IP address 23.235.240.152, where USD is the local currency and the local language is English. Wondermomwannabe.com has the potential to be earning an estimated $6 USD per day from advertising revenue. If wondermomwannabe.com was to be sold it would possibly be worth $4,030 USD (based on the daily revenue potential of the website over a 24 month period). Wondermomwannabe.com is quite popular with an estimated 1,932 daily unique visitors. This report was last updated 10th November, 2021.

About wondermomwannabe.com

Site Preview: wondermomwannabe.com wondermomwannabe.com
Title: Helping Busy Moms Do More With Less Stress
Description: Helping ordinary moms on their path of imperfection, making strides towards being wonder moms.
Keywords and Tags: blogs, wiki
Related Terms: attractive moms, banged moms, eg moms, helping, horny moms, moms exploited, moms rising, nacked moms, one moms
Fav Icon:
Age: Over 11 years old
Domain Created: 16th January, 2013
Domain Updated: 16th May, 2019
Domain Expires: 16th January, 2022
Review

Snoop Score

3/5 (Great!)

Valuation

$4,030 USD
Note: All valuation figures are estimates.

Popularity

Modest
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 349,441
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 1,932
Monthly Visitors: 58,804
Yearly Visitors: 705,180
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $6 USD
Monthly Revenue: $168 USD
Yearly Revenue: $2,010 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: wondermomwannabe.com 20
Domain Name: wondermomwannabe 16
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 2.35 seconds
Load Time Comparison: Faster than 37% of sites

PageSpeed Insights

Avg. (All Categories) 81
Performance 100
Accessibility 88
Best Practices 87
SEO 83
Progressive Web App 45
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://wondermomwannabe.com/
Updated: 10th November, 2021
Simulate loading on desktop
100

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for wondermomwannabe.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 0.5 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 0.8 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 0.5 s
The timing of the largest text or image that is painted.
Time to Interactive — 1.2 s
The time taken for the page to become fully interactive.
Total Blocking Time — 60 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0.029
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Max Potential First Input Delay — 110 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.5 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://wondermomwannabe.com/
http/1.1
0
165.37399985828
401
0
301
text/html
https://wondermomwannabe.com/
h2
166.27099993639
508.43099993654
47783
224021
200
text/html
Document
https://wondermomwannabe.com/wp-content/cache/min/1/ac7340f4d535c62618721a1e1d1fa9b8.css
h2
526.57099999487
916.83100000955
44377
269861
200
text/css
Stylesheet
https://wondermomwannabe.com/wp-includes/js/jquery/jquery.min.js?ver=3.6.0
h2
528.3899998758
772.36599987373
31396
89521
200
application/x-javascript
Script
https://wondermomwannabe.com/wp-content/plugins/convertkit/resources/frontend/jquery.cookie.min.js?ver=1.4.0
h2
557.00099980459
797.48800001107
1302
1667
200
application/x-javascript
Script
https://www.googletagmanager.com/gtag/js?id=UA-38753763-1
h2
557.23499995656
575.20699989982
37181
92541
200
application/javascript
Script
https://www.googletagmanager.com/gtag/js?id=G-BD4T2VJGK0
h2
557.45399999432
580.9209998697
62313
167054
200
application/javascript
Script
https://ads.adthrive.com/sites/597a513699fdd44462802f6e/ads.min.js?referrer=https%3A%2F%2Fwondermomwannabe.com%2F&cb=60
h2
557.8089999035
687.25399998948
18401
66054
200
application/javascript
Script
https://www.googletagmanager.com/gtm.js?id=GTM-M4Z8MC9
h2
558.09999979101
579.83800000511
41396
107274
200
application/javascript
Script
data
563.92299989238
564.06199978665
0
68
200
image/svg+xml
Image
data
566.3840000052
566.50600000285
0
67
200
image/svg+xml
Image
data
568.59699985944
568.70800000615
0
68
200
image/svg+xml
Image
https://wondermomwannabe.com/wp-content/plugins/social-rocket-pro/core/assets/webfonts/fa-brands-400.woff2
h2
577.9189998284
894.09999991767
77238
76736
200
text/plain
Font
data
616.18399992585
616.28399998881
0
68
200
image/svg+xml
Image
data
618.25999990106
618.36299998686
0
68
200
image/svg+xml
Image
data
621.15899985656
621.27899983898
0
70
200
image/svg+xml
Image
data
623.74099995941
623.89299995266
0
68
200
image/svg+xml
Image
https://wondermomwannabe.com/wp-content/plugins/wp-rocket/assets/js/lazyload/16.1/lazyload.min.js
h2
625.81499991938
858.26799995266
3258
7890
200
application/x-javascript
Script
https://app.slickstream.com/d/page-boot-data?site=QLMXN188&url=https%3A%2F%2Fwondermomwannabe.com%2F
h2
674.85799989663
861.24899983406
1079
0
200
application/json
Fetch
https://ads.adthrive.com/builds/core/944ec7b/js/adthrive.min.js?threshold=0&deployment=stable&cb=1636563326502
h2
762.91899988428
775.58499993756
112782
473555
200
application/javascript
Script
https://wondermomwannabe.com/wp-content/uploads/2021/06/logo-wmw-300x113-1.png
h2
941.57199980691
1189.0939997975
12450
11943
200
image/png
Image
https://wondermomwannabe.com/wp-content/uploads/2021/10/Chocolate-Cherry-Cookies-square-500x500.jpg
h2
941.76899990998
1080.5059999693
32980
32472
200
image/jpeg
Image
https://wondermomwannabe.com/wp-content/uploads/2021/10/Thanksgiving-placemats-4-500x500.png
h2
942.18899984844
1066.3869997952
112544
112036
200
image/png
Image
https://wondermomwannabe.com/wp-content/uploads/2021/09/Air-Fryer-Monte-Cristo-square-500x500.jpg
h2
942.47699994594
1125.2269998658
31001
30493
200
image/jpeg
Image
https://wondermomwannabe.com/wp-content/uploads/2021/10/Instant-Pot-Tortellini-Soup-square-500x500.jpg
h2
943.5049998574
1216.3149998523
20022
19514
200
image/jpeg
Image
https://c.slickstream.com/app/2.2.11/boot-loader.js
h2
1034.4719998538
1059.7599998582
5048
0
200
application/javascript
Fetch
blob:https://wondermomwannabe.com/10e88421-4ba9-4284-870e-83deaacaba84
blob
1069.8329999577
1073.9060000051
0
12731
200
application/javascript
Script
https://c.slickstream.com/app/2.2.11/app.js
h2
1078.9820000064
1115.6029999256
112238
508657
200
application/javascript
Fetch
blob:https://wondermomwannabe.com/d9d173df-6d13-4b9c-8f92-205bfe0420c5
blob
1128.826999804
1135.3809998836
0
508657
200
application/javascript
Script
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
551.434
11.285
566.181
15.463
584.973
23.381
608.379
32.373
650.083
13.286
665.391
16.56
682.433
26.874
719.643
10.458
730.151
9.126
739.666
17.242
758.529
8.297
766.844
25.609
794.849
6.34
820.408
21.846
849.006
104.958
958.133
7.183
975.98
6.06
984.671
15.027
999.979
66.133
1175.673
77.554
1471.057
6.427
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Opportunities

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Wondermomwannabe.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images — Potential savings of 71 KiB
Images can slow down the page's load time. Wondermomwannabe.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://wondermomwannabe.com/wp-content/uploads/2021/10/Thanksgiving-placemats-4-500x500.png
112036
42114
https://wondermomwannabe.com/wp-content/uploads/2021/10/Chocolate-Cherry-Cookies-square-500x500.jpg
32472
12206
https://wondermomwannabe.com/wp-content/uploads/2021/09/Air-Fryer-Monte-Cristo-square-500x500.jpg
30493
11462
https://wondermomwannabe.com/wp-content/uploads/2021/10/Instant-Pot-Tortellini-Soup-square-500x500.jpg
19514
7335
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Wondermomwannabe.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Wondermomwannabe.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Wondermomwannabe.com should consider minifying JS files.
Reduce unused CSS — Potential savings of 42 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Wondermomwannabe.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://wondermomwannabe.com/wp-content/cache/min/1/ac7340f4d535c62618721a1e1d1fa9b8.css
44377
42773
Reduce unused JavaScript — Potential savings of 142 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://ads.adthrive.com/builds/core/944ec7b/js/adthrive.min.js?threshold=0&deployment=stable&cb=1636563326502
112782
38660
https://www.googletagmanager.com/gtag/js?id=G-BD4T2VJGK0
62313
35206
https://www.googletagmanager.com/gtm.js?id=GTM-M4Z8MC9
41396
25320
https://wondermomwannabe.com/wp-includes/js/jquery/jquery.min.js?ver=3.6.0
31396
23567
https://www.googletagmanager.com/gtag/js?id=UA-38753763-1
37181
22738
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 73 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://wondermomwannabe.com/wp-content/uploads/2021/10/Thanksgiving-placemats-4-500x500.png
112036
66157.15
https://wondermomwannabe.com/wp-content/uploads/2021/10/Chocolate-Cherry-Cookies-square-500x500.jpg
32472
8269.3
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 340 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://wondermomwannabe.com/
343.151
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Wondermomwannabe.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://wondermomwannabe.com/
190
https://wondermomwannabe.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Wondermomwannabe.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 5 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://ads.adthrive.com/builds/core/944ec7b/js/adthrive.min.js?threshold=0&deployment=stable&cb=1636563326502
4898
https://wondermomwannabe.com/
167
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids enormous network payloads — Total size was 786 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://ads.adthrive.com/builds/core/944ec7b/js/adthrive.min.js?threshold=0&deployment=stable&cb=1636563326502
112782
https://wondermomwannabe.com/wp-content/uploads/2021/10/Thanksgiving-placemats-4-500x500.png
112544
https://c.slickstream.com/app/2.2.11/app.js
112238
https://wondermomwannabe.com/wp-content/plugins/social-rocket-pro/core/assets/webfonts/fa-brands-400.woff2
77238
https://www.googletagmanager.com/gtag/js?id=G-BD4T2VJGK0
62313
https://wondermomwannabe.com/
47783
https://wondermomwannabe.com/wp-content/cache/min/1/ac7340f4d535c62618721a1e1d1fa9b8.css
44377
https://www.googletagmanager.com/gtm.js?id=GTM-M4Z8MC9
41396
https://www.googletagmanager.com/gtag/js?id=UA-38753763-1
37181
https://wondermomwannabe.com/wp-content/uploads/2021/10/Chocolate-Cherry-Cookies-square-500x500.jpg
32980
Avoids an excessive DOM size — 520 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
520
Maximum DOM Depth
div.uagb-post__inner-wrap > div.uagb-post__image > a > img.attachment-wprm-metadata-1_1
15
Maximum Child Elements
body.home
56
Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Wondermomwannabe.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.3 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://wondermomwannabe.com/
259.73
50.139
11.426
https://ads.adthrive.com/builds/core/944ec7b/js/adthrive.min.js?threshold=0&deployment=stable&cb=1636563326502
104.986
90.081
9.499
blob:https://wondermomwannabe.com/d9d173df-6d13-4b9c-8f92-205bfe0420c5
99.466
50.073
42.239
Unattributable
83.058
18.124
0.184
https://www.googletagmanager.com/gtag/js?id=UA-38753763-1
52.084
47.542
2.148
Minimizes main-thread work — 0.7 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
311.041
Other
132.014
Style & Layout
81.657
Script Parsing & Compilation
77.038
Parse HTML & CSS
38.145
Rendering
33.113
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 20 requests • 786 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
20
805190
Script
8
308029
Image
5
208997
Other
4
118766
Font
1
77238
Document
1
47783
Stylesheet
1
44377
Media
0
0
Third-party
8
390438
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
SHOW DETAILS
140890
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
div.uagb-post__inner-wrap > div.uagb-post__image > a > img.attachment-wprm-metadata-1_1
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
div.uagb-post__inner-wrap > div.uagb-post__image > a > img.attachment-wprm-metadata-1_1
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
Chocolate Cherry Cookies Thanksgiving Placemats Air Fryer Monte Cristo
0.028786918012871
div.inside-navigation > div.main-nav > ul#menu-about > li#menu-item-56369
1.2458080467929E-5
div.inside-navigation > div.main-nav > ul#menu-about > li#menu-item-56370
1.2250445793464E-5
div.inside-navigation > div.main-nav > ul#menu-about > li#menu-item-56371
1.2250445793464E-5
div.inside-navigation > div.main-nav > ul#menu-about > li#menu-item-56368
1.2042811118998E-5
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoid long main-thread tasks — 2 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://ads.adthrive.com/builds/core/944ec7b/js/adthrive.min.js?threshold=0&deployment=stable&cb=1636563326502
1116
105
blob:https://wondermomwannabe.com/d9d173df-6d13-4b9c-8f92-205bfe0420c5
564
78
Avoid non-composited animations — 3 animated elements found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element Name
See More Easy Recipes
See More Printables
See More Homemaking
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of wondermomwannabe.com on mobile screens.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Diagnostics

Serve static assets with an efficient cache policy — 6 resources found
Wondermomwannabe.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://ads.adthrive.com/builds/core/944ec7b/js/adthrive.min.js?threshold=0&deployment=stable&cb=1636563326502
3600000
112782
https://ads.adthrive.com/sites/597a513699fdd44462802f6e/ads.min.js?referrer=https%3A%2F%2Fwondermomwannabe.com%2F&cb=60
3600000
18401
https://wondermomwannabe.com/wp-content/plugins/social-rocket-pro/core/assets/webfonts/fa-brands-400.woff2
2592000000
77238
https://wondermomwannabe.com/wp-includes/js/jquery/jquery.min.js?ver=3.6.0
2592000000
31396
https://wondermomwannabe.com/wp-content/plugins/wp-rocket/assets/js/lazyload/16.1/lazyload.min.js
2592000000
3258
https://wondermomwannabe.com/wp-content/plugins/convertkit/resources/frontend/jquery.cookie.min.js?ver=1.4.0
2592000000
1302

Diagnostics

Avoid `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Source
SHOW DETAILS
88

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of wondermomwannabe.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Wondermomwannabe.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements
parenting
Learn more about me →
AN ELITE CAFEMEDIA FAMILY & PARENTING PUBLISHER

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
div.inside-article > div.entry-content > div.about > img.alignleft
Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
87

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that wondermomwannabe.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
script-src directive is missing. This can allow the execution of unsafe scripts.
script-src
High
Missing object-src allows the injection of plugins that execute unsafe scripts. Consider setting object-src to 'none' if you can.
object-src
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
LitElement
2.5.1
jQuery
3.6.0
WordPress
5.8.1
core-js
core-js-global@3.8.0; core-js-pure@3.8.0; core-js-global@2.6.11
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://c.amazon-adsystem.com/aax2/apstag.js
https://c.amazon-adsystem.com/aax2/apstag.js.map
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://wondermomwannabe.com/
Allowed

Audits

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
SHOW DETAILS
%cVideoUtils::getPlacementElement color: #999; font-weight: bold; Error: PSNF: body.single does not exist on the page at Function.e.getPlacementElement (https://ads.adthrive.com/builds/core/944ec7b/js/adthrive.min.js?threshold=0&deployment=stable&cb=1636563326502:3:363866) at https://ads.adthrive.com/builds/core/944ec7b/js/adthrive.min.js?threshold=0&deployment=stable&cb=1636563326502:3:409273 at Array.map (<anonymous>) at r._checkPlayerSelectorOnPage (https://ads.adthrive.com/builds/core/944ec7b/js/adthrive.min.js?threshold=0&deployment=stable&cb=1636563326502:3:409223) at r._determineAutoplayPlayers (https://ads.adthrive.com/builds/core/944ec7b/js/adthrive.min.js?threshold=0&deployment=stable&cb=1636563326502:3:412500) at r._initializePlayers (https://ads.adthrive.com/builds/core/944ec7b/js/adthrive.min.js?threshold=0&deployment=stable&cb=1636563326502:3:408920) at r.init (https://ads.adthrive.com/builds/core/944ec7b/js/adthrive.min.js?threshold=0&deployment=stable&cb=1636563326502:3:408714) at r.init (https://ads.adthrive.com/builds/core/944ec7b/js/adthrive.min.js?threshold=0&deployment=stable&cb=1636563326502:3:84398) at i.init (https://ads.adthrive.com/builds/core/944ec7b/js/adthrive.min.js?threshold=0&deployment=stable&cb=1636563326502:3:417738) at i.init (https://ads.adthrive.com/builds/core/944ec7b/js/adthrive.min.js?threshold=0&deployment=stable&cb=1636563326502:3:84398)
SHOW DETAILS
Access to XMLHttpRequest at 'https://g2.gumgum.com/hbid/imp?pubcid=824ac565-a0bd-43eb-ac05-2b92590f0df3&t=g95nznmj&pi=2&uspConsent=1---&schain=1.0%2C1!cafemedia.com%2C597a513699fdd44462802f6e%2C1%2C%2C%2C&vw=1350&vh=940&sw=800&sh=600&pu=https%3A%2F%2Fwondermomwannabe.com%2F&ce=true&dpr=1&jcsi=%7B%22t%22%3A0%2C%22rq%22%3A8%2C%22pbv%22%3A%225.14.0%22%7D&ogu=https%3A%2F%2Fwondermomwannabe.com%2F&ns=9933&gpid=%2F18190176%2FAdThrive_Footer_1%2F597a513699fdd44462802f6e' from origin 'https://wondermomwannabe.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
SHOW DETAILS
Failed to load resource: net::ERR_FAILED
SHOW DETAILS
WebSocket connection to 'wss://c05b-wss.app.slickstream.com/socket?site=QLMXN188' failed: Error in connection establishment: net::ERR_NAME_NOT_RESOLVED
SHOW DETAILS
WebSocket connection to 'wss://c05b-wss.app.slickstream.com/socket?site=QLMXN188' failed: Error in connection establishment: net::ERR_NAME_NOT_RESOLVED
83

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for wondermomwannabe.com. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of wondermomwannabe.com on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

Document does not have a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
div.inside-article > div.entry-content > div.about > img.alignleft

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
45

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of wondermomwannabe.com. This includes details about web app manifests.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of wondermomwannabe.com on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 72
Performance 56
Accessibility 89
Best Practices 80
SEO 86
Progressive Web App 50
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://wondermomwannabe.com/
Updated: 10th November, 2021
Simulate loading on mobile
56

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for wondermomwannabe.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 1.5 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 2.5 s
The time taken for the page contents to be visibly populated.

Other

First Meaningful Paint — 1.5 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://wondermomwannabe.com/
http/1.1
0
231.28900001757
401
0
301
text/html
https://wondermomwannabe.com/
h2
231.75000003539
611.27300001681
47783
224021
200
text/html
Document
https://wondermomwannabe.com/wp-content/cache/min/1/ac7340f4d535c62618721a1e1d1fa9b8.css
h2
622.29699990712
1074.2359999567
44377
269861
200
text/css
Stylesheet
https://wondermomwannabe.com/wp-includes/js/jquery/jquery.min.js?ver=3.6.0
h2
623.34299995564
1005.0480000209
31396
89521
200
application/x-javascript
Script
https://wondermomwannabe.com/wp-content/plugins/convertkit/resources/frontend/jquery.cookie.min.js?ver=1.4.0
h2
642.94699998572
925.51500000991
1302
1667
200
application/x-javascript
Script
https://www.googletagmanager.com/gtag/js?id=UA-38753763-1
h2
643.08399986476
672.78899997473
37182
92541
200
application/javascript
Script
https://www.googletagmanager.com/gtag/js?id=G-BD4T2VJGK0
h2
643.24299991131
664.22299994156
62310
167054
200
application/javascript
Script
https://ads.adthrive.com/sites/597a513699fdd44462802f6e/ads.min.js?referrer=https%3A%2F%2Fwondermomwannabe.com%2F&cb=13
h2
643.33399990574
712.2420000378
18673
67517
200
application/javascript
Script
https://www.googletagmanager.com/gtm.js?id=GTM-M4Z8MC9
h2
643.52499996312
668.57800004072
41396
107274
200
application/javascript
Script
data
648.03199982271
648.13999994658
0
68
200
image/svg+xml
Image
data
649.55700002611
649.65000003576
0
67
200
image/svg+xml
Image
data
650.88899992406
650.98199993372
0
68
200
image/svg+xml
Image
https://wondermomwannabe.com/wp-content/plugins/social-rocket-pro/core/assets/webfonts/fa-brands-400.woff2
h2
655.27500002645
1068.2479999959
77238
76736
200
text/plain
Font
data
673.15099993721
673.24399994686
0
68
200
image/svg+xml
Image
data
674.79499988258
674.88599987701
0
68
200
image/svg+xml
Image
data
677.04300000332
677.13900003582
0
70
200
image/svg+xml
Image
data
678.54700004682
678.63600002602
0
68
200
image/svg+xml
Image
https://wondermomwannabe.com/wp-content/plugins/wp-rocket/assets/js/lazyload/16.1/lazyload.min.js
h2
690.98600000143
933.72999993153
3258
7890
200
application/x-javascript
Script
https://app.slickstream.com/d/page-boot-data?site=QLMXN188&url=https%3A%2F%2Fwondermomwannabe.com%2F
h2
718.32600003108
839.54499987885
1079
0
200
application/json
Fetch
https://ads.adthrive.com/builds/core/944ec7b/js/adthrive.min.js?threshold=0&deployment=stable&cb=1636563347515
h2
770.8509999793
794.57399994135
112782
473555
200
application/javascript
Script
https://c.slickstream.com/app/2.2.11/boot-loader.js
h2
893.61699996516
926.54199991375
5048
0
200
application/javascript
Fetch
blob:https://wondermomwannabe.com/c1c1e104-b098-4609-a9a0-0a7d17c5cf6d
blob
930.36899995059
931.50099995546
0
12731
200
application/javascript
Script
https://c.slickstream.com/app/2.2.11/app.js
h2
934.86599996686
1011.9099998847
112237
0
200
application/javascript
Fetch
https://wondermomwannabe.com/wp-content/uploads/2021/06/logo-wmw-mobile-1.png
h2
939.82900003903
1080.9100000188
10474
9968
200
image/png
Image
https://wondermomwannabe.com/wp-content/uploads/2021/10/Chocolate-Cherry-Cookies-square.jpg
h2
939.99699992128
1270.1530000195
131195
130686
200
image/jpeg
Image
https://wondermomwannabe.com/wp-content/uploads/2021/10/Thanksgiving-placemats-4.png
h2
940.80999982543
1520.8449999336
241549
241041
200
image/png
Image
blob:https://wondermomwannabe.com/d6557862-c5ce-49f1-977d-a5994be9c6d9
blob
1029.5440000482
1030.999999959
0
508657
200
application/javascript
Script
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
640.584
6.664
649.621
10.895
662.634
15.691
678.339
13.644
696.983
8.92
705.92
10.713
719.857
22.484
750.669
11.279
762.207
5.09
767.325
5.979
773.868
10.599
784.487
8.361
842.154
64.842
1037.997
14.08
1058.433
50.468
1110.445
5.447
1121.895
9.179
1131.218
39.319
1328.707
21.876
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Opportunities

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Wondermomwannabe.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Wondermomwannabe.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Wondermomwannabe.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Wondermomwannabe.com should consider minifying JS files.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 380 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://wondermomwannabe.com/
380.518
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Wondermomwannabe.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://wondermomwannabe.com/
630
https://wondermomwannabe.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Wondermomwannabe.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 5 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://ads.adthrive.com/builds/core/944ec7b/js/adthrive.min.js?threshold=0&deployment=stable&cb=1636563347515
4898
https://wondermomwannabe.com/
167
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids enormous network payloads — Total size was 957 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://wondermomwannabe.com/wp-content/uploads/2021/10/Thanksgiving-placemats-4.png
241549
https://wondermomwannabe.com/wp-content/uploads/2021/10/Chocolate-Cherry-Cookies-square.jpg
131195
https://ads.adthrive.com/builds/core/944ec7b/js/adthrive.min.js?threshold=0&deployment=stable&cb=1636563347515
112782
https://c.slickstream.com/app/2.2.11/app.js
112237
https://wondermomwannabe.com/wp-content/plugins/social-rocket-pro/core/assets/webfonts/fa-brands-400.woff2
77238
https://www.googletagmanager.com/gtag/js?id=G-BD4T2VJGK0
62310
https://wondermomwannabe.com/
47783
https://wondermomwannabe.com/wp-content/cache/min/1/ac7340f4d535c62618721a1e1d1fa9b8.css
44377
https://www.googletagmanager.com/gtm.js?id=GTM-M4Z8MC9
41396
https://www.googletagmanager.com/gtag/js?id=UA-38753763-1
37182
Avoids an excessive DOM size — 536 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
536
Maximum DOM Depth
div.uagb-post__inner-wrap > div.uagb-post__image > a > img.attachment-wprm-metadata-1_1
15
Maximum Child Elements
body.home
56
Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Wondermomwannabe.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.9 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://wondermomwannabe.com/
739.48
136.624
28.628
blob:https://wondermomwannabe.com/d6557862-c5ce-49f1-977d-a5994be9c6d9
265.128
126.076
116.94
https://ads.adthrive.com/builds/core/944ec7b/js/adthrive.min.js?threshold=0&deployment=stable&cb=1636563347515
259.496
217.864
27.744
Unattributable
200.836
39.536
0.508
https://www.googletagmanager.com/gtag/js?id=G-BD4T2VJGK0
134.34
118.836
11.224
https://wondermomwannabe.com/wp-includes/js/jquery/jquery.min.js?ver=3.6.0
56.268
43.536
6.364
Minimizes main-thread work — 1.8 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
748.98
Other
335.292
Script Parsing & Compilation
213.544
Style & Layout
192.212
Rendering
162.028
Parse HTML & CSS
102.584
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 18 requests • 957 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
18
979680
Image
3
383218
Script
8
308299
Other
4
118765
Font
1
77238
Document
1
47783
Stylesheet
1
44377
Media
0
0
Third-party
8
390707
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
SHOW DETAILS
140888
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
div.uagb-post__inner-wrap > div.uagb-post__image > a > img.attachment-wprm-metadata-1_1
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
div.uagb-post__inner-wrap > div.uagb-post__image > a > img.attachment-wprm-metadata-1_1
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
Helping Busy Moms Do More With Less Stress Latest Posts Chocolate Cherry Cookie…
0.33150965920071
Menu
0.11487958487153
Helping Busy Moms Do More With Less Stress Latest Posts Chocolate Cherry Cookie…
0.02490234375
Open Search Bar
0.0077315784104015
div.inside-navigation > div.main-nav > ul#menu-about > li#menu-item-56372
8.6534288194444E-5
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoid long main-thread tasks — 5 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://ads.adthrive.com/builds/core/944ec7b/js/adthrive.min.js?threshold=0&deployment=stable&cb=1636563347515
4934
259
blob:https://wondermomwannabe.com/d6557862-c5ce-49f1-977d-a5994be9c6d9
1578
202
https://wondermomwannabe.com/
630
88
https://wondermomwannabe.com/
1780
79
https://wondermomwannabe.com/wp-includes/js/jquery/jquery.min.js?ver=3.6.0
5193
56
Avoid non-composited animations — 3 animated elements found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element Name
See More Easy Recipes
See More Printables
See More Homemaking
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of wondermomwannabe.com on mobile screens.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

Time to Interactive — 5.2 s
The time taken for the page to become fully interactive.
Total Blocking Time — 390 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Opportunities

Properly size images — Potential savings of 134 KiB
Images can slow down the page's load time. Wondermomwannabe.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://wondermomwannabe.com/wp-content/uploads/2021/10/Chocolate-Cherry-Cookies-square.jpg
130686
79695
https://wondermomwannabe.com/wp-content/uploads/2021/10/Thanksgiving-placemats-4.png
241041
57950
Reduce unused CSS — Potential savings of 42 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Wondermomwannabe.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://wondermomwannabe.com/wp-content/cache/min/1/ac7340f4d535c62618721a1e1d1fa9b8.css
44377
42834
Reduce unused JavaScript — Potential savings of 142 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://ads.adthrive.com/builds/core/944ec7b/js/adthrive.min.js?threshold=0&deployment=stable&cb=1636563347515
112782
38523
https://www.googletagmanager.com/gtag/js?id=G-BD4T2VJGK0
62310
34418
https://www.googletagmanager.com/gtm.js?id=GTM-M4Z8MC9
41396
25399
https://wondermomwannabe.com/wp-includes/js/jquery/jquery.min.js?ver=3.6.0
31396
23567
https://www.googletagmanager.com/gtag/js?id=UA-38753763-1
37182
23405

Diagnostics

Serve static assets with an efficient cache policy — 6 resources found
Wondermomwannabe.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://ads.adthrive.com/builds/core/944ec7b/js/adthrive.min.js?threshold=0&deployment=stable&cb=1636563347515
3600000
112782
https://ads.adthrive.com/sites/597a513699fdd44462802f6e/ads.min.js?referrer=https%3A%2F%2Fwondermomwannabe.com%2F&cb=13
3600000
18673
https://wondermomwannabe.com/wp-content/plugins/social-rocket-pro/core/assets/webfonts/fa-brands-400.woff2
2592000000
77238
https://wondermomwannabe.com/wp-includes/js/jquery/jquery.min.js?ver=3.6.0
2592000000
31396
https://wondermomwannabe.com/wp-content/plugins/wp-rocket/assets/js/lazyload/16.1/lazyload.min.js
2592000000
3258
https://wondermomwannabe.com/wp-content/plugins/convertkit/resources/frontend/jquery.cookie.min.js?ver=1.4.0
2592000000
1302

Other

First Contentful Paint (3G) — 2862 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Metrics

Largest Contentful Paint — 5.3 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.479
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Max Potential First Input Delay — 260 ms
Users could experience a delay when interacting with the page.

Opportunities

Serve images in next-gen formats — Potential savings of 194 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://wondermomwannabe.com/wp-content/uploads/2021/10/Thanksgiving-placemats-4.png
241041
147481.65
https://wondermomwannabe.com/wp-content/uploads/2021/10/Chocolate-Cherry-Cookies-square.jpg
130686
51289.55

Diagnostics

Avoid `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Source
SHOW DETAILS
SHOW DETAILS
89

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of wondermomwannabe.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Wondermomwannabe.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements
parenting
Learn more about me →
AN ELITE CAFEMEDIA FAMILY & PARENTING PUBLISHER

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
div.inside-article > div.entry-content > div.about > img.alignleft
Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
80

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that wondermomwannabe.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
script-src directive is missing. This can allow the execution of unsafe scripts.
script-src
High
Missing object-src allows the injection of plugins that execute unsafe scripts. Consider setting object-src to 'none' if you can.
object-src
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
LitElement
2.5.1
jQuery
3.6.0
WordPress
5.8.1
core-js
core-js-global@3.8.0; core-js-pure@3.8.0; core-js-global@2.6.11
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://c.amazon-adsystem.com/aax2/apstag.js
https://c.amazon-adsystem.com/aax2/apstag.js.map
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://wondermomwannabe.com/
Allowed

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
https://wondermomwannabe.com/wp-content/uploads/2021/06/logo-wmw-mobile-1.png
197 x 75
250 x 95
394 x 150

Audits

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
SHOW DETAILS
%cVideoUtils::getPlacementElement color: #999; font-weight: bold; Error: ESNF: .entry-content > p does not exist on the page at Function.e.getPlacementElement (https://ads.adthrive.com/builds/core/944ec7b/js/adthrive.min.js?threshold=0&deployment=stable&cb=1636563347515:3:364035) at https://ads.adthrive.com/builds/core/944ec7b/js/adthrive.min.js?threshold=0&deployment=stable&cb=1636563347515:3:409273 at Array.map (<anonymous>) at r._checkPlayerSelectorOnPage (https://ads.adthrive.com/builds/core/944ec7b/js/adthrive.min.js?threshold=0&deployment=stable&cb=1636563347515:3:409223) at r._determineAutoplayPlayers (https://ads.adthrive.com/builds/core/944ec7b/js/adthrive.min.js?threshold=0&deployment=stable&cb=1636563347515:3:412581) at r._initializePlayers (https://ads.adthrive.com/builds/core/944ec7b/js/adthrive.min.js?threshold=0&deployment=stable&cb=1636563347515:3:408920) at r.init (https://ads.adthrive.com/builds/core/944ec7b/js/adthrive.min.js?threshold=0&deployment=stable&cb=1636563347515:3:408714) at r.init (https://ads.adthrive.com/builds/core/944ec7b/js/adthrive.min.js?threshold=0&deployment=stable&cb=1636563347515:3:84398) at i.init (https://ads.adthrive.com/builds/core/944ec7b/js/adthrive.min.js?threshold=0&deployment=stable&cb=1636563347515:3:417738) at i.init (https://ads.adthrive.com/builds/core/944ec7b/js/adthrive.min.js?threshold=0&deployment=stable&cb=1636563347515:3:84398)
SHOW DETAILS
WebSocket connection to 'wss://c05b-wss.app.slickstream.com/socket?site=QLMXN188' failed: Error in connection establishment: net::ERR_NAME_NOT_RESOLVED
SHOW DETAILS
WebSocket connection to 'wss://c05b-wss.app.slickstream.com/socket?site=QLMXN188' failed: Error in connection establishment: net::ERR_NAME_NOT_RESOLVED
86

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for wondermomwannabe.com. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of wondermomwannabe.com on mobile screens.
Document uses legible font sizes — 99.48% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
SHOW DETAILS
.ns-9ai4k-v-0 .ns-9ai4k-e-10
0.36%
11px
SHOW DETAILS
.ns-9ai4k-e-17
0.16%
11px
SHOW DETAILS
99.48%
≥ 12px
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

Document does not have a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
div.inside-article > div.entry-content > div.about > img.alignleft

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
50

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of wondermomwannabe.com. This includes details about web app manifests.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of wondermomwannabe.com on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 23.235.240.152
Continent: North America
Country: United States
United States Flag
Region: Arizona
City: Phoenix
Longitude: -112.0749
Latitude: 33.4532
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
SECURED SERVERS LLC
Registration

Domain Registrant

Private Registration: No
Name:
Organization:
Country:
City:
State:
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
GoDaddy.com, LLC 23.203.184.117
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating:
WOT Trustworthiness:
WOT Child Safety:
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: wondermomwannabe.com
Issued By: R3
Valid From: 15th October, 2021
Valid To: 13th January, 2022
Subject: CN = wondermomwannabe.com
Hash: 652e4258
Issuer: CN = R3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x03B0BCD322857C001F8F9640DF9C3ADF08C7
Serial Number (Hex): 03B0BCD322857C001F8F9640DF9C3ADF08C7
Valid From: 15th October, 2024
Valid To: 13th January, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 2.23.140.1.2.1
Policy: 1.3.6.1.4.1.44947.1.1.1
CPS: http://cps.letsencrypt.org
Authority Information Access: OCSP - URI:http://r3.o.lencr.org
CA Issuers - URI:http://r3.i.lencr.org/
SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : DF:A5:5E:AB:68:82:4F:1F:6C:AD:EE:B8:5F:4E:3E:5A:
EA:CD:A2:12:A4:6A:5E:8E:3B:12:C0:20:44:5C:2A:73
Timestamp : Oct 15 10:16:32.006 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:37:A7:21:F6:54:36:57:EC:0C:F7:E8:1C:
92:47:B4:55:F0:3F:50:DF:82:17:CA:24:D3:5A:A8:DC:
49:D1:A0:6F:02:21:00:E3:66:F8:71:5F:17:15:7C:5C:
3E:CA:02:E9:F3:55:94:44:28:A4:A3:71:F7:87:DC:55:
94:69:EB:32:4A:DC:11
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 46:A5:55:EB:75:FA:91:20:30:B5:A2:89:69:F4:F3:7D:
11:2C:41:74:BE:FD:49:B8:85:AB:F2:FC:70:FE:6D:47
Timestamp : Oct 15 10:16:32.046 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:99:03:6B:27:2C:8C:CE:F8:83:26:4B:
79:0F:A8:66:BF:13:DE:3B:55:24:3A:BC:E6:2E:77:D1:
77:1D:08:8F:BA:02:20:18:7E:2E:1D:A5:44:17:55:40:
13:67:B5:84:03:34:2C:3F:3C:53:65:C2:BF:BF:CA:5C:
33:28:26:73:40:E8:DD
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:www.wondermomwannabe.com
DNS:wondermomwannabe.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
wondermomwannabe.com. 38.29.223.182 IN 1200
wondermomwannabe.com. 38.29.223.52 IN 1200
wondermomwannabe.com. 38.29.223.152 IN 1200
wondermomwannabe.com. 23.235.240.152 IN 1200

NS Records

Host Nameserver Class TTL
wondermomwannabe.com. ns2.techsurgeons.com. IN 1200
wondermomwannabe.com. ns.techsurgeons.com. IN 1200

MX Records

Priority Host Server Class TTL
10 wondermomwannabe.com. mail.techsurgeons.com. IN 1200

SOA Records

Domain Name Primary NS Responsible Email TTL
wondermomwannabe.com. ns.techsurgeons.com. root.wondermomwannabe.com. 1200

TXT Records

Host Value Class TTL
wondermomwannabe.com. google-site-verification=KdPham2qA_AL-jnd4KUwTdcX7xTLMzgMQ1SuaSCZZYg IN 1200
wondermomwannabe.com. facebook-domain-verification=36a7y3lg2b1hktc0x9ek2iwf34v2jv IN 1200
wondermomwannabe.com. v=spf1 IN 1200
wondermomwannabe.com. google-site-verification=IKSXgw-ZHinKavOYHQSsMYxHcWyykreM9ZiOmVp8rmY IN 1200

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 10th November, 2021
Server: Apache
Cache-Control: max-age=0
Expires: 10th November, 2021
Content-Type: text/html; charset=UTF-8
X-Frame-Options: SAMEORIGIN
Upgrade: h2,h2c
Connection: Upgrade
Last-Modified: 10th November, 2021
Access-Control-Allow-Origin: *
Cross-Origin-Embedder-Policy: unsafe-none
Vary: Accept-Encoding
Content-Security-Policy: block-all-mixed-content
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff

Whois Lookup

Created: 16th January, 2013
Changed: 16th May, 2019
Expires: 16th January, 2022
Registrar: GoDaddy.com, LLC
Status: ok
Nameservers: ns.techsurgeons.com
ns2.techsurgeons.com
Owner Organization: TechSurgeons LLC
Owner State: Arizona
Owner Country: US
Owner Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=wondermomwannabe.com
Admin Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=wondermomwannabe.com
Tech Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=wondermomwannabe.com
Full Whois: Domain Name: wondermomwannabe.com
Registry Domain ID: 1773989262_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: http://www.godaddy.com
Updated Date: 2019-05-16T00:53:38Z
Creation Date: 2013-01-16T16:40:22Z
Registrar Registration Expiration Date: 2022-01-16T16:40:22Z
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: abuse@godaddy.com
Registrar Abuse Contact Phone: +1.4806242505
Domain Status: ok https://icann.org/epp#ok
Registrant Organization: TechSurgeons LLC
Registrant State/Province: Arizona
Registrant Country: US
Registrant Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=wondermomwannabe.com
Tech Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=wondermomwannabe.com
Admin Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=wondermomwannabe.com
Name Server: NS.TECHSURGEONS.COM
Name Server: NS2.TECHSURGEONS.COM
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2021-11-10T16:55:22Z <<<
For more information on Whois status codes, please visit https://icann.org/epp

TERMS OF USE: The data contained in this registrar's Whois database, while believed by the
registrar to be reliable, is provided "as is" with no guarantee or warranties regarding its
accuracy. This information is provided for the sole purpose of assisting you in obtaining
information about domain name registration records. Any use of this data for any other purpose
is expressly forbidden without the prior written permission of this registrar. By submitting
an inquiry, you agree to these terms and limitations of warranty. In particular, you agree not
to use this data to allow, enable, or otherwise support the dissemination or collection of this
data, in part or in its entirety, for any purpose, such as transmission by e-mail, telephone,
postal mail, facsimile or other means of mass unsolicited, commercial advertising or solicitations
of any kind, including spam. You further agree not to use this data to enable high volume, automated
or robotic electronic processes designed to collect or compile this data for any purpose, including
mining this data for your own personal or commercial purposes. Failure to comply with these terms
may result in termination of access to the Whois database. These terms may be subject to modification
at any time without notice.
View Raw Whois

Nameservers

Name IP Address
ns.techsurgeons.com 38.29.223.12
ns2.techsurgeons.com 167.114.131.177
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address

Domain Valuation Snoop Score
mythinkbiglife.com
$607 USD 1/5
Love W3 Snoop?
Update Now

wondermomwannabe.com Infographic

wondermomwannabe.com by the numbers infographic

Recently Updated

caniphish.com
github.io
moviesera.com
poki.com
bonk.io
lolibooru.org
vlxx.com
tremor.com
aniwave.to
vidoevo.com

Recently Viewed

thecityoflights.net
aaaacccc.com
l-eco.fr
jor-alkhaer.com
quicksellthemes.com
genprison.net
biasy.net
smeeo.com
ziffdavisenterprise.com
exrsa.com