whatkatysaid.com

whatkatysaid.com is SSL secured

Free website and domain report on whatkatysaid.com

Last Updated: 27th September, 2022 Update Now
Overview

Snoop Summary for whatkatysaid.com

This is a free and comprehensive report about whatkatysaid.com. The domain whatkatysaid.com is currently hosted on a server located in United Kingdom with the IP address 185.151.30.172, where the local currency is GBP and English is the local language. Our records indicate that whatkatysaid.com is privately registered by Domains By Proxy, LLC. Whatkatysaid.com has the potential to be earning an estimated $1 USD per day from advertising revenue. If whatkatysaid.com was to be sold it would possibly be worth $952 USD (based on the daily revenue potential of the website over a 24 month period). Whatkatysaid.com is somewhat popular with an estimated 453 daily unique visitors. This report was last updated 27th September, 2022.

About whatkatysaid.com

Site Preview: whatkatysaid.com whatkatysaid.com
Title: Magnifying Glass
Description: A family lifestyle blog by mother of three, Katy. With organisation tips, parenting advice and motherhood tales, Katy keeps it real and honest, always.
Keywords and Tags: sports
Related Terms: katy, katy carr, katy keene, katy mixon feet, katy perry, katy perry naked, katy perry nip slip, katy perry witness itunes plus
Fav Icon:
Age: Over 9 years old
Domain Created: 4th May, 2014
Domain Updated: 5th May, 2022
Domain Expires: 4th May, 2024
Review

Snoop Score

1/5

Valuation

$952 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 1,910,012
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: 453
Monthly Visitors: 13,788
Yearly Visitors: 165,345
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $39 USD
Yearly Revenue: $471 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: whatkatysaid.com 16
Domain Name: whatkatysaid 12
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 14.23 seconds
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 87
Performance 87
Accessibility 95
Best Practices 92
SEO 83
PWA 78
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.whatkatysaid.com
Updated: 27th September, 2022

1.95 seconds
First Contentful Paint (FCP)
74%
17%
9%

0.00 seconds
First Input Delay (FID)
100%
0%
0%

Simulate loading on desktop
87

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for whatkatysaid.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.
Time to Interactive — 1.1 s
The time taken for the page to become fully interactive.
Total Blocking Time — 10 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).
Largest Contentful Paint — 0.6 s
The timing of the largest text or image that is painted.

Audits

Max Potential First Input Delay — 60 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://whatkatysaid.com/
http/1.1
0
242.95299989171
357
0
301
text/html
https://www.whatkatysaid.com/
h2
243.32999996841
808.78899991512
44516
257744
200
text/html
Document
https://www.whatkatysaid.com/wp-includes/js/jquery/jquery.min.js?ver=3.6.0
h2
819.22900001518
1233.7410000619
36469
89521
200
application/javascript
Script
https://www.whatkatysaid.com/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.3.2
h2
819.49499994516
927.45999991894
4981
11224
200
application/javascript
Script
https://www.whatkatysaid.com/wp-content/mvt-js/1/dffa195b546cf1dfd52f2206955eb892.min.js
h2
1105.1860000007
1245.1479998417
8376
27232
200
application/javascript
Script
https://scripts.mediavine.com/tags/what-katy-said.js?ver=8d4adf60b12ad5636daad6da04283c46
h2
1238.6920000426
1256.2879999168
16425
62942
200
application/javascript
Script
https://www.googletagmanager.com/gtag/js?id=UA-51596054-1
h2
1256.9819998462
1296.1059999652
42994
108638
200
application/javascript
Script
https://www.whatkatysaid.com/wp-content/plugins/pixelyoursite/dist/scripts/jquery.bind-first-0.2.3.min.js?ver=8d4adf60b12ad5636daad6da04283c46
h2
820.11500000954
1103.7049998995
1088
1317
200
application/javascript
Script
https://www.whatkatysaid.com/wp-content/plugins/pixelyoursite/dist/scripts/js.cookie-2.1.3.min.js?ver=2.1.3
h2
1257.1620000526
1386.0829998739
1278
1709
200
application/javascript
Script
https://www.whatkatysaid.com/wp-content/plugins/pixelyoursite/dist/scripts/public.js?ver=9.2.0
h2
1257.3130000383
1460.2619998623
19958
93702
200
application/javascript
Script
https://www.whatkatysaid.com/wp-content/uploads/2021/07/WKSHEADER2021-1.png.webp
h2
1257.4670000467
1403.7349999417
29646
29262
200
image/webp
Image
https://www.fleamailapp.co.uk/badge.js
h2
1257.5749999378
1584.3769998755
983
464
200
text/javascript
Script
https://www.whatkatysaid.com/wp-content/plugins/social-pug/assets/dist/front-end-pro.2.16.2.js?ver=2.16.2
h2
1257.6549998485
1378.2649999484
10237
30383
200
application/javascript
Script
https://www.whatkatysaid.com/wp-content/themes/mediavine-trellis/assets/dist/main.0.15.3.js?ver=0.15.3
h2
1257.7710000332
1353.9390000515
7161
17391
200
application/javascript
Script
https://www.whatkatysaid.com/wp-content/mvt-critical/1/cb70d11b873b3bf32b45b16ffa4d1263.ad601f38680643e6cb44eae6b6fe9772.secondary.css?ver=8d4adf60b12ad5636daad6da04283c46
h2
1258.0289999023
1391.7079998646
41300
264591
200
text/css
Stylesheet
https://assets.flodesk.com/universal.js?v=1664266996262
http/1.1
1257.9240000341
1319.3049998954
37550
103574
200
application/javascript
Script
https://assets.flodesk.com/universal.mjs?v=832133460
http/1.1
1256.0759999324
1317.6829998847
32147
86574
200
application/javascript
Script
data
1268.0480000563
1268.1380000431
0
121
200
image/svg+xml
Image
data
1279.1569998953
1279.2670000345
0
121
200
image/svg+xml
Image
data
1281.8609999958
1281.9629998412
0
121
200
image/svg+xml
Image
data
1297.3559999373
1297.4419998936
0
121
200
image/svg+xml
Image
data
1298.9039998502
1299.0210000426
0
121
200
image/svg+xml
Image
data
1300.1399999484
1300.206999993
0
121
200
image/svg+xml
Image
data
1301.1839999817
1301.2659999076
0
121
200
image/svg+xml
Image
data
1302.1949999966
1302.2549999878
0
121
200
image/svg+xml
Image
data
1303.159999894
1303.2609999646
0
121
200
image/svg+xml
Image
data
1304.2389999609
1304.2959999293
0
121
200
image/svg+xml
Image
data
1305.4239999037
1305.4789998569
0
121
200
image/svg+xml
Image
https://scripts.mediavine.com/tags/2.76.7/wrapper.min.js?bust=-854382441
h2
1315.9709998872
1336.1589999404
48410
150983
200
application/javascript
Script
https://exchange.mediavine.com/usersync.min.js?s2sVersion=production
h2
1316.2899999879
1341.6389999911
4663
14252
200
application/javascript
Script
https://keywords.mediavine.com/keyword/web.keywords.js?pageUrl=https://www.whatkatysaid.com/
h2
1316.5619999636
1337.6869999338
1259
468
200
text/html
Script
https://form.flodesk.com/forms/62461cdbb3be600de2a270ff
h2
1390.711999964
1470.1040000655
4421
27001
200
text/html
XHR
https://faves.grow.me/main.js
h2
1421.209000051
1436.4599999972
3184
6220
200
application/javascript
Script
https://scripts.mediavine.com/tags/7837/298709a27976adfbf880.min.js
h2
1450.6490000058
1466.3889999501
9075
23055
200
application/javascript
Script
https://scripts.mediavine.com/tags/6748/7fb443bfa86d2d4a7e57.min.js
h2
1451.4389999676
1466.6309999302
5396
11708
200
application/javascript
Script
https://scripts.mediavine.com/tags/3824/c3ad9c1f20de9518b78b.min.js
h2
1452.4949998595
1467.2119999304
2697
3141
200
application/javascript
Script
https://assets.flodesk.com/1794.d6899499a6ed3d47a422.js
http/1.1
1489.0979998745
1573.3529999852
12091
31388
200
application/javascript
Script
https://assets.flodesk.com/7650.20265e7e57ddbf7cd98d.js
http/1.1
1489.6329999901
1542.2660000622
4647
10818
200
application/javascript
Script
https://www.whatkatysaid.com/wp-content/themes/mediavine-trellis/assets/dist/sw.0.15.3.js
h2
1509.4749999698
1619.3929999135
866
921
200
application/javascript
Script
data
1509.6040000208
1509.7310000565
0
44
200
image/webp
Image
https://www.whatkatysaid.com/wp-admin/admin-ajax.php?action=pys_get_gdpr_filters_values
h2
1615.0459998753
3452.2579999175
765
182
200
application/json
XHR
https://api.grow.me/sites/b64fcfca-77b9-45ba-a97e-1c8e2354d042/config
h2
1617.7509999834
1633.2570000086
1457
2128
200
application/json
Fetch
https://api.grow.me/graphql?query=query+GetIsGdpr+%7B%0A++isRequestFromGdprCountry%0A%7D&variables=%7B%7D&operationName=GetIsGdpr
h2
1618.5510000214
1633.8450000621
603
44
200
application/json
Fetch
https://api.grow.me/versions
h2
1618.7559999526
1633.6169999558
542
32
200
application/json
Fetch
data
1645.7529999316
1645.993999904
0
1544
200
image/svg+xml
Image
data
1647.357000038
1647.5569999311
0
699
200
image/svg+xml
Image
https://www.whatkatysaid.com/wp-content/uploads/2022/08/LIFESTYLE-MENU.png.webp
h2
1664.2839999404
1772.6310000289
42867
42482
200
image/webp
Image
https://www.whatkatysaid.com/wp-content/uploads/2022/06/maintain.png.webp
h2
1664.5579999313
1850.1949999481
64103
63718
200
image/webp
Image
https://www.whatkatysaid.com/wp-content/uploads/2022/08/Motherhood-4.png.webp
h2
1664.8549998645
1791.8050000444
42875
42490
200
image/webp
Image
https://www.whatkatysaid.com/wp-content/uploads/2021/03/Screenshot-2021-03-04-at-12.39.13-720x540.png.webp
h2
1665.6569999177
1870.1460000593
43959
43574
200
image/webp
Image
https://www.whatkatysaid.com/wp-content/uploads/2017/11/Lost-in-motherhood-768x510.jpg.webp
h2
1666.0139998421
1860.4929998983
23817
23432
200
image/webp
Image
https://www.whatkatysaid.com/wp-content/uploads/2022/06/Plants-735x490.jpeg.webp
h2
1666.2399999332
1849.0480000619
38427
38042
200
image/webp
Image
https://www.whatkatysaid.com/wp-content/uploads/2022/02/woman-g132451c10_1920-735x490.jpg.webp
h2
1666.7019999586
1859.2999998946
29804
29420
200
image/webp
Image
https://www.whatkatysaid.com/wp-content/uploads/2022/01/self-care-sunday-735x490.jpg.webp
h2
1666.9939998537
1934.7069999203
31656
31272
200
image/webp
Image
https://www.whatkatysaid.com/wp-content/uploads/2022/04/dress-2583113_1920-735x490.jpg.webp
h2
1667.4539998639
1959.7719998565
24290
23906
200
image/webp
Image
https://www.whatkatysaid.com/wp-content/uploads/2022/05/pexels-pixabay-247115-735x490.jpg.webp
h2
1667.7639998961
2021.7279999051
17454
17070
200
image/webp
Image
https://www.whatkatysaid.com/wp-content/uploads/2022/04/pexels-artem-beliaikin-994523-735x490.jpg.webp
h2
1668.4270000551
1771.8779998831
17901
17516
200
image/webp
Image
https://www.whatkatysaid.com/wp-content/uploads/2021/05/Femme-Luxe-Clothing-735x489.jpg.webp
h2
1669.6219998412
1856.8849998992
23833
23448
200
image/webp
Image
https://www.whatkatysaid.com/wp-content/uploads/2021/04/My-Stitch-Fix-delivery-735x489.jpg.webp
h2
1669.7370000184
1981.4780000597
28214
27830
200
image/webp
Image
https://www.fleamailapp.co.uk/badge.png
h2
1685.3099998552
2002.3499999661
7110
6478
200
image/png
Image
https://faves.grow.me/app.7.104.0.js
h2
1709.7620000131
1726.7670000438
16988
51601
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
h2
4313.6020000093
4318.195000058
20450
49672
200
text/javascript
Script
https://www.google-analytics.com/collect?v=1&_v=j97&aip=1&a=115067356&t=pageview&_s=1&dl=https%3A%2F%2Fwww.whatkatysaid.com%2F&ul=en-us&de=UTF-8&dt=What%20Katy%20Said%20-%20A%20UK%20Family%20Lifestyle%20Blog&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=YEBAAUAB~&cid=1631683177.1664266999&tid=UA-51596054-1&_gid=159743628.1664266999&gtm=2ou9l0&z=393902996
h2
4337.9170000553
4341.1880000494
597
35
200
image/gif
Image
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)
812.95
13.919
1239.832
11.024
1251.321
8.276
1259.607
6.292
1270.258
7.65
1277.974
5.462
1284.028
8.218
1292.318
16.009
1308.862
8.947
1318.025
18.913
1343.072
9.472
1356.147
8.017
1371.579
20.167
1391.777
63.94
1457.782
12.645
1471.304
10.752
1485.425
5.578
1491.149
8.447
1501.246
36.84
1538.193
6.476
1544.683
31.207
1576.611
7.095
1584.898
23.235
1608.142
8.359
1621.336
32.873
1654.233
15.701
1678.384
6.315
1687.239
16.482
1727.255
33.315
1764.185
12.108
1794.899
8.91
1876.939
8.315
4307.951
6.588
4323.49
15.257
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.

Other

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Whatkatysaid.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images — Potential savings of 171 KiB
Images can slow down the page's load time. Whatkatysaid.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.whatkatysaid.com/wp-content/uploads/2022/06/maintain.png.webp
63718
56756
https://www.whatkatysaid.com/wp-content/uploads/2022/08/Motherhood-4.png.webp
42490
37847
https://www.whatkatysaid.com/wp-content/uploads/2022/08/LIFESTYLE-MENU.png.webp
42482
37840
https://www.whatkatysaid.com/wp-content/uploads/2021/07/WKSHEADER2021-1.png.webp
29262
27292
https://www.whatkatysaid.com/wp-content/uploads/2021/03/Screenshot-2021-03-04-at-12.39.13-720x540.png.webp
43574
15687
Defer offscreen images — Potential savings of 6 KiB
Time to Interactive can be slowed down by resources on the page. Whatkatysaid.com should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.fleamailapp.co.uk/badge.png
6478
6478
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Whatkatysaid.com should consider minifying CSS files.
Minify JavaScript — Potential savings of 10 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Whatkatysaid.com should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.whatkatysaid.com/wp-content/plugins/pixelyoursite/dist/scripts/public.js?ver=9.2.0
19958
10225
Reduce unused CSS — Potential savings of 39 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Whatkatysaid.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://www.whatkatysaid.com/wp-content/mvt-critical/1/cb70d11b873b3bf32b45b16ffa4d1263.ad601f38680643e6cb44eae6b6fe9772.secondary.css?ver=8d4adf60b12ad5636daad6da04283c46
41300
39628
Reduce unused JavaScript — Potential savings of 20 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://www.googletagmanager.com/gtag/js?id=UA-51596054-1
42994
20964
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
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 570 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://www.whatkatysaid.com/
566.451
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Whatkatysaid.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://whatkatysaid.com/
190
https://www.whatkatysaid.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Whatkatysaid.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 28 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://assets.flodesk.com/universal.js?v=1664266996262
15520
https://assets.flodesk.com/1794.d6899499a6ed3d47a422.js
7537
https://www.whatkatysaid.com/wp-content/plugins/pixelyoursite/dist/scripts/public.js?ver=9.2.0
5560
https://faves.grow.me/app.7.104.0.js
55
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 889 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.whatkatysaid.com/wp-content/uploads/2022/06/maintain.png.webp
64103
https://scripts.mediavine.com/tags/2.76.7/wrapper.min.js?bust=-854382441
48410
https://www.whatkatysaid.com/
44516
https://www.whatkatysaid.com/wp-content/uploads/2021/03/Screenshot-2021-03-04-at-12.39.13-720x540.png.webp
43959
https://www.googletagmanager.com/gtag/js?id=UA-51596054-1
42994
https://www.whatkatysaid.com/wp-content/uploads/2022/08/Motherhood-4.png.webp
42875
https://www.whatkatysaid.com/wp-content/uploads/2022/08/LIFESTYLE-MENU.png.webp
42867
https://www.whatkatysaid.com/wp-content/mvt-critical/1/cb70d11b873b3bf32b45b16ffa4d1263.ad601f38680643e6cb44eae6b6fe9772.secondary.css?ver=8d4adf60b12ad5636daad6da04283c46
41300
https://www.whatkatysaid.com/wp-content/uploads/2022/06/Plants-735x490.jpeg.webp
38427
https://assets.flodesk.com/universal.js?v=1664266996262
37550
Uses efficient cache policy on static assets — 1 resource found
Whatkatysaid.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://www.google-analytics.com/analytics.js
7200000
20450
Avoid chaining critical requests — 3 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Whatkatysaid.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.1 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://www.whatkatysaid.com/
302.165
35.238
2.305
Unattributable
72.887
18.201
0.191
https://scripts.mediavine.com/tags/2.76.7/wrapper.min.js?bust=-854382441
61.85
40.117
2.144
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
250.468
Style & Layout
167.572
Other
118.614
Rendering
66.794
Parse HTML & CSS
31.429
Script Parsing & Compilation
17.189
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 — 49 requests • 889 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
49
909887
Image
16
466553
Script
25
349373
Document
1
44516
Stylesheet
1
41300
Other
6
8145
Media
0
0
Font
0
0
Third-party
22
273689
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)
87925
0
42994
0
21047
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
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `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.
Avoid long main-thread tasks — 1 long task 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://scripts.mediavine.com/tags/2.76.7/wrapper.min.js?bust=-854382441
1033
64
Avoid non-composited animations — 1 animated element found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element Name
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 whatkatysaid.com on mobile screens.
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.

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

Speed Index — 1.4 s
The time taken for the page contents to be visibly populated.

Other

Avoid an excessive DOM size — 902 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
902
Maximum DOM Depth
14
Maximum Child Elements
38

Metrics

Cumulative Layout Shift — 0.416
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Largest Contentful Paint image was lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
95

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of whatkatysaid.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.
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.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<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 alternate 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"]`
Whatkatysaid.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Navigation

Heading elements are not 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.
Failing Elements

Names and labels

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.
92

Best Practices

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

Audits

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

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.6.0
WordPress
core-js
core-js-global@3.23.4; core-js-global@3.23.4
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
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://www.whatkatysaid.com/wp-content/themes/mediavine-trellis/assets/dist/sw.0.15.3.js
https://www.whatkatysaid.com/wp-content/themes/mediavine-trellis/assets/dist/sw.0.15.3.js.map
https://www.whatkatysaid.com/wp-content/themes/mediavine-trellis/assets/dist/main.0.15.3.js?ver=0.15.3
https://www.whatkatysaid.com/wp-content/themes/mediavine-trellis/assets/dist/main.0.15.3.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://whatkatysaid.com/
Allowed
83

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for whatkatysaid.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 whatkatysaid.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.
Document has 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 have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
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.
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

Links do not have descriptive text — 31 links found
Make use of descriptive link text to assist search engines in understanding the content.

Crawling and Indexing

Links are not 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.

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.
78

PWA

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

Installable

Web app manifest and service worker meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.

PWA Optimized

Registers 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.
Sets 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
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 whatkatysaid.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.

PWA Optimized

Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
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) 88
Performance 91
Accessibility 96
Best Practices 93
SEO 79
Progressive Web App 83
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.whatkatysaid.com
Updated: 12th November, 2021

3.22 seconds
First Contentful Paint (FCP)
51%
21%
28%

0.02 seconds
First Input Delay (FID)
95%
4%
1%

Simulate loading on mobile
91

Performance

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

Metrics

Largest Contentful Paint — 2.0 s
The timing of the largest text or image that is painted.
Total Blocking Time — 180 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.002
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 — 2.0 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://whatkatysaid.com/
http/1.1
0
183.14400012605
426
0
301
text/html
https://www.whatkatysaid.com/
h2
183.82000015117
382.10500008427
37855
202818
200
text/html
Document
https://www.whatkatysaid.com/wp-includes/js/jquery/jquery.min.js?ver=3.6.0
h2
395.90899995528
545.15899997205
36549
89521
200
application/javascript
Script
https://www.whatkatysaid.com/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.3.2
h2
396.12399996258
490.11600017548
5061
11224
200
application/javascript
Script
https://www.whatkatysaid.com/wp-content/mvt-js/1/80529ec8dbf91e771ccca3646fe9300b.min.js
h2
491.75800010562
585.15699999407
8404
26952
200
application/javascript
Script
https://scripts.mediavine.com/tags/what-katy-said.js?ver=5f289cb0b5ee379539e051e7b0e78f6f
h2
552.28800000623
568.8960000407
13997
50127
200
application/javascript
Script
https://www.googletagmanager.com/gtag/js?id=UA-51596054-1
h2
573.02800007164
585.70699999109
36703
91830
200
application/javascript
Script
https://www.whatkatysaid.com/wp-content/plugins/pixelyoursite/dist/scripts/jquery.bind-first-0.2.3.min.js?ver=5f289cb0b5ee379539e051e7b0e78f6f
h2
396.57600014471
488.31100016832
1161
1317
200
application/javascript
Script
https://www.whatkatysaid.com/wp-content/plugins/pixelyoursite/dist/scripts/js.cookie-2.1.3.min.js?ver=2.1.3
h2
573.1959999539
669.1160001792
1352
1709
200
application/javascript
Script
https://www.whatkatysaid.com/wp-content/plugins/pixelyoursite/dist/scripts/public.js?ver=8.2.8
h2
573.41199996881
847.07999997772
16416
79083
200
application/javascript
Script
https://www.whatkatysaid.com/wp-content/mvt-critical/1/cb70d11b873b3bf32b45b16ffa4d1263.30ba76ad1e2e7ea3e5f43caff15f7ebe.secondary.css?ver=5f289cb0b5ee379539e051e7b0e78f6f
h2
574.2480000481
680.27699994855
28897
193475
200
text/css
Stylesheet
https://www.whatkatysaid.com/wp-content/uploads/2021/07/WKSHEADER2021-1-960x320.png.webp
h2
573.54500005022
692.80400010757
18701
18242
200
image/webp
Image
https://www.fleamailapp.co.uk/badge.js
h2
573.6630000174
990.08200014941
939
408
200
application/javascript
Script
https://www.whatkatysaid.com/wp-content/plugins/social-pug/assets/dist/front-end-pro.2.14.1.js?ver=2.14.1
h2
573.80500016734
667.81400004402
9565
27998
200
application/javascript
Script
https://www.whatkatysaid.com/wp-content/themes/mediavine-trellis/assets/dist/main.0.14.3.js?ver=0.14.3
h2
574.0030000452
668.73300005682
7166
17125
200
application/javascript
Script
https://assets.flodesk.com/universal.js?v=1636720088166
http/1.1
574.10500012338
664.7520000115
21726
58927
200
application/javascript
Script
data
580.10000013746
580.19700017758
0
121
200
image/svg+xml
Image
data
581.6679999698
581.74100005999
0
121
200
image/svg+xml
Image
data
582.97800016589
583.05000001565
0
121
200
image/svg+xml
Image
data
584.15700006299
584.22800013795
0
121
200
image/svg+xml
Image
data
585.5000000447
585.56400006637
0
121
200
image/svg+xml
Image
data
586.75300003961
586.83200017549
0
121
200
image/svg+xml
Image
data
588.16000004299
588.22500007227
0
121
200
image/svg+xml
Image
data
589.4200000912
589.50000000186
0
121
200
image/svg+xml
Image
data
590.70700011216
590.7760001719
0
121
200
image/svg+xml
Image
data
592.2159999609
592.28800004348
0
121
200
image/svg+xml
Image
https://scripts.mediavine.com/tags/2.72.4/wrapper.min.js?bust=1073967775
h2
656.88100014813
674.97000005096
49556
163963
200
application/javascript
Script
https://exchange.mediavine.com/usersync.min.js?s2sVersion=rc-3-t
h2
657.14300004765
711.71000017785
4620
13816
200
application/javascript
Script
https://keywords.mediavine.com/keyword/web.keywords.js?pageUrl=https://www.whatkatysaid.com/
h2
657.71199995652
672.34200006351
642
330
200
text/html
Script
https://scripts.mediavine.com/tags/7611/31866cc7a6dcb387a087.min.js
h2
758.84400005452
774.44500010461
11195
29342
200
application/javascript
Script
https://scripts.mediavine.com/tags/ccpa/d63d5c43141171755488.min.js
h2
759.57100000232
774.80500005186
7723
25146
200
application/javascript
Script
https://faves.grow.me/main.js
h2
794.15800003335
808.83600004017
2338
3841
200
application/javascript
Script
https://scripts.mediavine.com/tags/6458/49149efa5549d1498308.min.js
h2
822.3210000433
837.123000063
5773
13050
200
application/javascript
Script
https://scripts.mediavine.com/tags/7214/96fcefa8f60c9d51a494.min.js
h2
822.73600017652
837.59200014174
6557
16522
200
application/javascript
Script
https://scripts.mediavine.com/tags/2598/4f1a6bc29360d1134055.min.js
h2
823.42800009064
838.61099998467
4741
12263
200
application/javascript
Script
https://api.grow.me/versions
h2
836.58200013451
851.16000007838
568
31
200
application/json
Fetch
data
854.20499998145
854.43400009535
0
1544
200
image/svg+xml
Image
data
855.73900002055
855.89700005949
0
699
200
image/svg+xml
Image
https://www.whatkatysaid.com/wp-content/themes/mediavine-trellis/assets/dist/sw.0.14.3.js
h2
888.42400000431
982.12600010447
909
852
200
application/javascript
Script
data
890.11500007473
890.2750001289
0
44
200
image/webp
Image
https://faves.grow.me/app.7.47.3.js
h2
901.89200011082
919.74300006405
34638
110024
200
application/javascript
Script
https://www.whatkatysaid.com/wp-admin/admin-ajax.php?action=pys_get_gdpr_filters_values
h2
936.48200016469
1431.0870000627
758
182
200
application/json
XHR
https://www.whatkatysaid.com/wp-content/uploads/2021/03/MOTHERHOOD-WELLBEING-900x900.png.webp
h2
952.99100014381
1104.5369999483
45693
45234
200
image/webp
Image
https://www.whatkatysaid.com/wp-content/uploads/2021/03/PARENTING-ADVICE-900x900.png.webp
h2
953.11200013384
1090.1750000194
36147
35688
200
image/webp
Image
https://www.whatkatysaid.com/wp-content/uploads/2021/03/HOME-ORGANISATION-900x900.png.webp
h2
953.28000001609
1098.5700001474
70174
69714
200
image/webp
Image
https://www.whatkatysaid.com/wp-content/uploads/2021/03/Screenshot-2021-03-04-at-12.39.13-720x540.png.webp
h2
953.54500017129
1057.4370000977
44032
43574
200
image/webp
Image
https://www.whatkatysaid.com/wp-content/uploads/2018/11/Gift-ideas-for-mums-900x598.jpg.webp
h2
953.75000010245
1067.1769999899
61274
60816
200
image/webp
Image
https://www.whatkatysaid.com/wp-content/uploads/2021/11/DSC_0272-900x585.jpg.webp
h2
953.91499996185
1085.4750000872
28735
28276
200
image/webp
Image
https://www.whatkatysaid.com/wp-content/uploads/2018/11/Mens-gift-guide-900x598.jpg.webp
h2
954.1470000986
1054.5159999747
36508
36050
200
image/webp
Image
https://api.grow.me/sites/b64fcfca-77b9-45ba-a97e-1c8e2354d042/config
h2
983.31300006248
998.23400005698
1289
1680
200
application/json
Fetch
https://www.fleamailapp.co.uk/badge.png
h2
994.11800014786
1405.0420001149
13492
12988
200
image/png
Image
https://www.google-analytics.com/analytics.js
h2
3644.7390001267
3649.4980000425
20474
50205
200
text/javascript
Script
https://www.google-analytics.com/collect?v=1&_v=j96&aip=1&a=1224440124&t=pageview&_s=1&dl=https%3A%2F%2Fwww.whatkatysaid.com%2F&ul=en-us&de=UTF-8&dt=Home%20-%20What%20Katy%20Said&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=YEBAAUAB~&cid=411191036.1636720091&tid=UA-51596054-1&_gid=1310996088.1636720091&gtm=2ouba1&z=1030823762
h2
3675.4150001798
3678.4560000524
440
35
200
image/gif
Image
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)
412.73
7.295
422.439
5.795
579.665
41.195
620.881
30.241
656.715
8.059
670.599
6.039
677.048
8.043
696.218
12.556
711.086
5.923
718.117
5.712
726.472
5.394
731.896
55.558
787.579
7.029
805.878
46.225
868.155
27.726
902.263
5.169
907.976
12.404
920.422
6.529
935.22
24.628
964.13
17.628
983.349
5.972
994.684
16.19
1021.547
23.857
1088.219
5.295
1104.799
6.654
3665.54
6.856
3681.89
20.972
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

Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Whatkatysaid.com should consider minifying CSS files.
Reduce unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
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 200 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://www.whatkatysaid.com/
199.278
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Whatkatysaid.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://whatkatysaid.com/
630
https://www.whatkatysaid.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Whatkatysaid.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.
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 716 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.whatkatysaid.com/wp-content/uploads/2021/03/HOME-ORGANISATION-900x900.png.webp
70174
https://www.whatkatysaid.com/wp-content/uploads/2018/11/Gift-ideas-for-mums-900x598.jpg.webp
61274
https://scripts.mediavine.com/tags/2.72.4/wrapper.min.js?bust=1073967775
49556
https://www.whatkatysaid.com/wp-content/uploads/2021/03/MOTHERHOOD-WELLBEING-900x900.png.webp
45693
https://www.whatkatysaid.com/wp-content/uploads/2021/03/Screenshot-2021-03-04-at-12.39.13-720x540.png.webp
44032
https://www.whatkatysaid.com/
37855
https://www.googletagmanager.com/gtag/js?id=UA-51596054-1
36703
https://www.whatkatysaid.com/wp-includes/js/jquery/jquery.min.js?ver=3.6.0
36549
https://www.whatkatysaid.com/wp-content/uploads/2018/11/Mens-gift-guide-900x598.jpg.webp
36508
https://www.whatkatysaid.com/wp-content/uploads/2021/03/PARENTING-ADVICE-900x900.png.webp
36147
Uses efficient cache policy on static assets — 3 resources found
Whatkatysaid.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://www.fleamailapp.co.uk/badge.png
1000
13492
https://www.google-analytics.com/analytics.js
7200000
20474
https://www.fleamailapp.co.uk/badge.js
262974000
939
Avoids an excessive DOM size — 704 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
704
Maximum DOM Depth
14
Maximum Child Elements
26
Avoid chaining critical requests — 3 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Whatkatysaid.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.8 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://www.whatkatysaid.com/
829.512
76.164
10.248
https://www.whatkatysaid.com/wp-includes/js/jquery/jquery.min.js?ver=3.6.0
245.8
186.984
5.988
Unattributable
199.224
19.856
0.528
https://scripts.mediavine.com/tags/2.72.4/wrapper.min.js?bust=1073967775
194.56
84.856
10.348
https://scripts.mediavine.com/tags/7611/31866cc7a6dcb387a087.min.js
184.628
90.504
2.188
https://scripts.mediavine.com/tags/2598/4f1a6bc29360d1134055.min.js
110.792
61.228
1.096
https://www.google-analytics.com/analytics.js
84.908
75.796
4.972
https://faves.grow.me/app.7.47.3.js
72.448
58.476
9.204
https://scripts.mediavine.com/tags/what-katy-said.js?ver=5f289cb0b5ee379539e051e7b0e78f6f
65.9
59.96
3.116
https://assets.flodesk.com/universal.js?v=1636720088166
50.224
44.216
4.236
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 — 40 requests • 716 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
40
733194
Image
10
355196
Script
24
308205
Document
1
37855
Stylesheet
1
28897
Other
4
3041
Media
0
0
Font
0
0
Third-party
19
237411
Minimize third-party usage — Third-party code blocked the main thread for 130 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)
104804
110.06
20914
22.12
36703
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
Avoid large layout shifts — 1 element found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.002339599609375
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `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.
Avoid long main-thread tasks — 9 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://scripts.mediavine.com/tags/2.72.4/wrapper.min.js?bust=1073967775
4045
111
https://scripts.mediavine.com/tags/7611/31866cc7a6dcb387a087.min.js
4906
92
https://www.google-analytics.com/analytics.js
4394
84
https://www.whatkatysaid.com/wp-includes/js/jquery/jquery.min.js?ver=3.6.0
3360
82
https://faves.grow.me/app.7.47.3.js
6378
65
https://www.whatkatysaid.com/
1583
60
https://scripts.mediavine.com/tags/2598/4f1a6bc29360d1134055.min.js
5148
55
https://assets.flodesk.com/universal.js?v=1636720088166
4676
50
https://www.whatkatysaid.com/wp-content/plugins/pixelyoursite/dist/scripts/public.js?ver=8.2.8
4560
50
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 whatkatysaid.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

First Contentful Paint — 2.0 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 3.6 s
The time taken for the page contents to be visibly populated.
Time to Interactive — 6.1 s
The time taken for the page to become fully interactive.

Opportunities

Eliminate render-blocking resources — Potential savings of 320 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Whatkatysaid.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://www.whatkatysaid.com/wp-includes/js/jquery/jquery.min.js?ver=3.6.0
36549
300
Properly size images — Potential savings of 58 KiB
Images can slow down the page's load time. Whatkatysaid.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.whatkatysaid.com/wp-content/uploads/2021/03/HOME-ORGANISATION-900x900.png.webp
69714
11984
https://www.whatkatysaid.com/wp-content/uploads/2021/07/WKSHEADER2021-1-960x320.png.webp
18242
11520
https://www.whatkatysaid.com/wp-content/uploads/2018/11/Gift-ideas-for-mums-900x598.jpg.webp
60816
10529
https://www.whatkatysaid.com/wp-content/uploads/2021/03/MOTHERHOOD-WELLBEING-900x900.png.webp
45234
7776
https://www.whatkatysaid.com/wp-content/uploads/2018/11/Mens-gift-guide-900x598.jpg.webp
36050
6241
https://www.whatkatysaid.com/wp-content/uploads/2021/03/PARENTING-ADVICE-900x900.png.webp
35688
6135
https://www.whatkatysaid.com/wp-content/uploads/2021/11/DSC_0272-900x585.jpg.webp
28276
4838
Defer offscreen images — Potential savings of 13 KiB
Time to Interactive can be slowed down by resources on the page. Whatkatysaid.com should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.fleamailapp.co.uk/badge.png
12988
12988
Minify JavaScript — Potential savings of 8 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Whatkatysaid.com should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.whatkatysaid.com/wp-content/plugins/pixelyoursite/dist/scripts/public.js?ver=8.2.8
16416
8338
Reduce unused CSS — Potential savings of 27 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Whatkatysaid.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://www.whatkatysaid.com/wp-content/mvt-critical/1/cb70d11b873b3bf32b45b16ffa4d1263.30ba76ad1e2e7ea3e5f43caff15f7ebe.secondary.css?ver=5f289cb0b5ee379539e051e7b0e78f6f
28897
27459
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 18 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://assets.flodesk.com/universal.js?v=1636720088166
12506
https://www.whatkatysaid.com/wp-content/plugins/pixelyoursite/dist/scripts/public.js?ver=8.2.8
5419
https://faves.grow.me/app.7.47.3.js
53

Diagnostics

Minimize main-thread work — 2.2 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
888.484
Style & Layout
611.864
Other
355.096
Rendering
207.132
Parse HTML & CSS
95.788
Script Parsing & Compilation
79

Other

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

Diagnostics

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
96

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of whatkatysaid.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.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<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"]`
Whatkatysaid.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

Names and labels

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.
93

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that whatkatysaid.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
jQuery
3.6.0
WordPress
core-js
core-js-global@3.16.0; core-js-pure@3.15.2
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
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://www.whatkatysaid.com/wp-content/themes/mediavine-trellis/assets/dist/sw.0.14.3.js
https://www.whatkatysaid.com/wp-content/themes/mediavine-trellis/assets/dist/sw.0.14.3.js.map
https://www.whatkatysaid.com/wp-content/themes/mediavine-trellis/assets/dist/main.0.14.3.js?ver=0.14.3
https://www.whatkatysaid.com/wp-content/themes/mediavine-trellis/assets/dist/main.0.14.3.js.map
https://scripts.mediavine.com/tags/what-katy-said.js?ver=5f289cb0b5ee379539e051e7b0e78f6f
https://scripts.mediavine.com/tags/launcher.min.js.map;
https://scripts.mediavine.com/tags/ccpa/d63d5c43141171755488.min.js
https://scripts.mediavine.com/tags/ccpa/d63d5c43141171755488.min.js.map
https://scripts.mediavine.com/tags/7611/31866cc7a6dcb387a087.min.js
https://scripts.mediavine.com/tags/7611/31866cc7a6dcb387a087.min.js.map
https://scripts.mediavine.com/tags/7214/96fcefa8f60c9d51a494.min.js
https://scripts.mediavine.com/tags/7214/96fcefa8f60c9d51a494.min.js.map
https://scripts.mediavine.com/tags/6458/49149efa5549d1498308.min.js
https://scripts.mediavine.com/tags/6458/49149efa5549d1498308.min.js.map
https://scripts.mediavine.com/tags/2598/4f1a6bc29360d1134055.min.js
https://scripts.mediavine.com/tags/2598/4f1a6bc29360d1134055.min.js.map
https://scripts.mediavine.com/tags/2.72.4/wrapper.min.js?bust=1073967775
https://scripts.mediavine.com/tags/2.72.4/wrapper.min.js.map
https://faves.grow.me/main.js
https://faves.grow.me/main.js.map
https://faves.grow.me/app.7.47.3.js
https://faves.grow.me/app.7.47.3.js.map
https://exchange.mediavine.com/usersync.min.js?s2sVersion=rc-3-t
https://exchange.mediavine.com/usersync.min.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://whatkatysaid.com/
Allowed
79

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for whatkatysaid.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 whatkatysaid.com on mobile screens.
Document uses legible font sizes — 100% 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
100.00%
≥ 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.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
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.
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.
Links do not have descriptive text — 25 links found
Make use of descriptive link text to assist search engines in understanding the content.

Crawling and Indexing

Links are not 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.

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.
83

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 whatkatysaid.com. This includes details about web app manifests.

Installable

Web app manifest and service worker meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.

PWA Optimized

Registers 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.
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.
Sets 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
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 whatkatysaid.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.

PWA Optimized

Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
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: 185.151.30.172
Continent: Europe
Country: United Kingdom
United Kingdom Flag
Region:
City:
Longitude: -0.1224
Latitude: 51.4964
Currencies: GBP
Languages: English

Web Hosting Provider

Name IP Address
Cloud Platform
Registration

Domain Registrant

Private Registration: Yes
Name: Registration Private
Organization: Domains By Proxy, LLC
Country: US
City: Tempe
State: Arizona
Post Code: 85284
Email: WHATKATYSAID.COM@domainsbyproxy.com
Phone: +1.4806242599
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
GoDaddy.com, LLC 23.196.70.224
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: *.whatkatysaid.com
Issued By: R3
Valid From: 17th September, 2022
Valid To: 16th December, 2022
Subject: CN = *.whatkatysaid.com
Hash: 0eea6b4f
Issuer: CN = R3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x04564A70A48213D9940A1C4B9A0A15E6293D
Serial Number (Hex): 04564A70A48213D9940A1C4B9A0A15E6293D
Valid From: 17th September, 2024
Valid To: 16th December, 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 : Sep 17 07:43:41.197 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:9C:D5:8E:4F:14:87:28:A1:23:10:87:
A6:92:9E:12:9B:A8:12:D3:38:DB:DC:25:1B:F8:62:2D:
91:6A:80:17:E9:02:21:00:C7:D9:CD:2E:A2:0D:1D:04:
55:55:82:D8:AB:C9:7A:57:33:E6:6A:F7:5F:33:4D:90:
4F:22:7B:B0:94:29:DF:E5
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 29:79:BE:F0:9E:39:39:21:F0:56:73:9F:63:A5:77:E5:
BE:57:7D:9C:60:0A:F8:F9:4D:5D:26:5C:25:5D:C7:84
Timestamp : Sep 17 07:43:41.191 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:94:6A:31:1F:40:2D:C4:5C:9A:1A:FD:
72:65:48:E0:6A:80:DE:32:B5:3C:64:41:F8:7F:48:B4:
2A:5A:26:8A:49:02:21:00:DF:5E:40:53:18:EE:E2:64:
E3:BF:8A:B0:79:90:13:A0:65:5F:C0:6C:8E:FE:C1:82:
5B:F0:2C:C4:C1:2D:D0:39
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:whatkatysaid.com
DNS:*.whatkatysaid.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
whatkatysaid.com. 185.151.30.172 IN 3600

NS Records

Host Nameserver Class TTL
whatkatysaid.com. ns1.lyricalhost.com. IN 3600
whatkatysaid.com. ns2.lyricalhost.com. IN 3600
whatkatysaid.com. ns3.lyricalhost.com. IN 3600
whatkatysaid.com. ns4.lyricalhost.com. IN 3600

AAAA Records

IP Address Class TTL
2a07:7800::172 IN 3600

MX Records

Priority Host Server Class TTL
10 whatkatysaid.com. mx.stackmail.com. IN 3600

SOA Records

Domain Name Primary NS Responsible Email TTL
whatkatysaid.com. ns1.lyricalhost.com. hostmaster.stackdns.com. 3600

TXT Records

Host Value Class TTL
whatkatysaid.com. v=spf1 IN 3600
whatkatysaid.com. bm-site-verification=e42f43c45a4bce999b50a0a260d60fd106c67587 IN 3600

HTTP Response Headers

HTTP-Code: HTTP/1.1 301 Moved Permanently
date: 27th September, 2022
content-type: text/html; charset=iso-8859-1
cache-control: max-age=2592000
server: Apache
location: https://www.whatkatysaid.com/
x-origin-cache-status: HIT
x-cdn-cache-status: HIT
x-via: ASH1

Whois Lookup

Created: 4th May, 2014
Changed: 5th May, 2022
Expires: 4th May, 2024
Registrar: GoDaddy.com, LLC
Status: clientTransferProhibited
clientUpdateProhibited
clientRenewProhibited
clientDeleteProhibited
Nameservers: ns1.lyricalhost.com
ns2.lyricalhost.com
ns3.lyricalhost.com
ns4.lyricalhost.com
Owner Name: Registration Private
Owner Organization: Domains By Proxy, LLC
Owner Street: DomainsByProxy.com
2155 E Warner Rd
Owner Post Code: 85284
Owner City: Tempe
Owner State: Arizona
Owner Country: US
Owner Phone: +1.4806242599
Owner Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=WHATKATYSAID.COM
Admin Name: Registration Private
Admin Organization: Domains By Proxy, LLC
Admin Street: DomainsByProxy.com
2155 E Warner Rd
Admin Post Code: 85284
Admin City: Tempe
Admin State: Arizona
Admin Country: US
Admin Phone: +1.4806242599
Admin Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=WHATKATYSAID.COM
Tech Name: Registration Private
Tech Organization: Domains By Proxy, LLC
Tech Street: DomainsByProxy.com
2155 E Warner Rd
Tech Post Code: 85284
Tech City: Tempe
Tech State: Arizona
Tech Country: US
Tech Phone: +1.4806242599
Tech Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=WHATKATYSAID.COM
Full Whois: Domain Name: WHATKATYSAID.COM
Registry Domain ID: 1857254792_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: https://www.godaddy.com
Updated Date: 2022-05-05T05:52:04Z
Creation Date: 2014-05-04T02:55:50Z
Registrar Registration Expiration Date: 2024-05-04T02:55:50Z
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: abuse@godaddy.com
Registrar Abuse Contact Phone: +1.4806242505
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Registry Registrant ID: Not Available From Registry
Registrant Name: Registration Private
Registrant Organization: Domains By Proxy, LLC
Registrant Street: DomainsByProxy.com
Registrant Street: 2155 E Warner Rd
Registrant City: Tempe
Registrant State/Province: Arizona
Registrant Postal Code: 85284
Registrant Country: US
Registrant Phone: +1.4806242599
Registrant Phone Ext:
Registrant Fax: +1.4806242598
Registrant Fax Ext:
Registrant Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=WHATKATYSAID.COM
Registry Admin ID: Not Available From Registry
Admin Name: Registration Private
Admin Organization: Domains By Proxy, LLC
Admin Street: DomainsByProxy.com
Admin Street: 2155 E Warner Rd
Admin City: Tempe
Admin State/Province: Arizona
Admin Postal Code: 85284
Admin Country: US
Admin Phone: +1.4806242599
Admin Phone Ext:
Admin Fax: +1.4806242598
Admin Fax Ext:
Admin Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=WHATKATYSAID.COM
Registry Tech ID: Not Available From Registry
Tech Name: Registration Private
Tech Organization: Domains By Proxy, LLC
Tech Street: DomainsByProxy.com
Tech Street: 2155 E Warner Rd
Tech City: Tempe
Tech State/Province: Arizona
Tech Postal Code: 85284
Tech Country: US
Tech Phone: +1.4806242599
Tech Phone Ext:
Tech Fax: +1.4806242598
Tech Fax Ext:
Tech Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=WHATKATYSAID.COM
Name Server: NS1.LYRICALHOST.COM
Name Server: NS2.LYRICALHOST.COM
Name Server: NS3.LYRICALHOST.COM
Name Server: NS4.LYRICALHOST.COM
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2022-09-27T08:23:12Z <<<
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.

Nameservers

Name IP Address
ns1.lyricalhost.com 35.197.225.59
ns2.lyricalhost.com 146.148.28.88
ns3.lyricalhost.com 35.198.79.191
ns4.lyricalhost.com 104.196.137.209
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
0/5
$43,192 USD 2/5
$998 USD 1/5
$447 USD 1/5