womensrunning.co.uk

womensrunning.co.uk is SSL secured

Free website and domain report on womensrunning.co.uk

Last Updated: 4th August, 2022 Update Now
Overview

Snoop Summary for womensrunning.co.uk

This is a free and comprehensive report about womensrunning.co.uk. The domain womensrunning.co.uk is currently hosted on a server located in United States with the IP address 172.67.181.80, where the local currency is USD and English is the local language. Womensrunning.co.uk has the potential to be earning an estimated $1 USD per day from advertising revenue. If womensrunning.co.uk was to be sold it would possibly be worth $1,025 USD (based on the daily revenue potential of the website over a 24 month period). Womensrunning.co.uk is somewhat popular with an estimated 488 daily unique visitors. This report was last updated 4th August, 2022.

About womensrunning.co.uk

Site Preview: womensrunning.co.uk womensrunning.co.uk
Title: Women's Running
Description: Women's running training advice for 5K, 10K, half-marathons and marathons, female-specific kit reviews, women's running shoe reviews and more from Women's Running magazine.
Keywords and Tags: internet services
Related Terms: and trail running, kereta terpakai bawah 10k, kihei running, maui running, running a business from home, running musique, running shoe store, running shoes for women, running store, running ubuntu directly from usb
Fav Icon:
Age: Over 12 years old
Domain Created: 29th November, 2012
Domain Updated: 27th June, 2022
Domain Expires: 29th November, 2023
Review

Snoop Score

1/5

Valuation

$1,025 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 1,288,598
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: 488
Monthly Visitors: 14,853
Yearly Visitors: 178,120
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $42 USD
Yearly Revenue: $508 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: womensrunning.co.uk 19
Domain Name: womensrunning 13
Extension (TLD): couk 4
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 78
Performance 97
Accessibility 95
Best Practices 83
SEO 92
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.womensrunning.co.uk/
Updated: 4th August, 2022
Simulate loading on desktop
97

Performance

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

Metrics

First Contentful Paint — 0.9 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 0.9 s
The time taken for the page to become fully interactive.
Speed Index — 1.3 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 0 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.9 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.003
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.9 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://womensrunning.co.uk/
http/1.1
0
71.052999992389
747
0
301
text/plain
https://womensrunning.co.uk/
http/1.1
71.498000004794
410.16199998558
795
0
301
text/html
https://www.womensrunning.co.uk/
h2
410.53799999645
882.55899999058
21633
127620
200
text/html
Document
https://www.womensrunning.co.uk/wp-content/cache/min/1/wp-content/themes/anthem/css/core.css?ver=1659539556
h2
891.94699999643
953.52600002661
9022
45057
200
text/css
Stylesheet
https://www.womensrunning.co.uk/wp-content/cache/min/1/wp-content/themes/anthem/css/responsive.css?ver=1659539556
h2
892.09099998698
974.14800000843
4030
13708
200
text/css
Stylesheet
https://www.womensrunning.co.uk/wp-content/cache/min/1/wp-content/themes/anthem/css/print.css?ver=1659539556
h2
892.26499997312
915.05200002575
1615
1887
200
text/css
Stylesheet
https://www.womensrunning.co.uk/wp-content/cache/min/1/vuo8oip.css?ver=1659539556
h2
892.48799998313
958.58699997189
1295
2084
200
text/css
Stylesheet
https://www.womensrunning.co.uk/wp-content/themes/anthem/js/jquery.min.js
h2
903.06600002805
987.68399999244
35234
95785
200
application/javascript
Script
https://www.womensrunning.co.uk/wp-content/cache/min/1/wp-content/themes/anthem/js/jquery.cookie.js?ver=1659539556
h2
903.30800000811
975.00699997181
1824
1921
200
application/javascript
Script
https://www.womensrunning.co.uk/wp-content/themes/anthem/js/slick.min.js
h2
903.58400001423
991.68199999258
11151
40090
200
application/javascript
Script
https://www.womensrunning.co.uk/wp-content/cache/min/1/wp-content/themes/anthem/js/slick.css?ver=1659539556
h2
893.02700001281
930.92100002104
1356
1322
200
text/css
Stylesheet
https://www.womensrunning.co.uk/wp-content/cache/min/1/wp-content/themes/anthem/js/global.js?ver=1659539556
h2
903.93299999414
988.19800000638
1995
3157
200
application/javascript
Script
https://www.womensrunning.co.uk/wp-content/plugins/wp-rocket/assets/js/lazyload/17.5/lazyload.min.js
h2
904.09199998248
960.45700000832
3810
8291
200
application/javascript
Script
data
906.33299999172
906.42199997092
0
66
200
image/svg+xml
Image
data
907.69999998156
907.79299999122
0
64
200
image/svg+xml
Image
data
910.98500002408
911.08699998586
0
69
200
image/svg+xml
Image
data
913.3879999863
913.4699999704
0
66
200
image/svg+xml
Image
data
914.84400001355
914.96800002642
0
66
200
image/svg+xml
Image
data
916.40699998243
916.50900000241
0
68
200
image/svg+xml
Image
data
928.81399998441
928.90599998645
0
68
200
image/svg+xml
Image
https://p.typekit.net/p.css?s=1&k=vuo8oip&ht=tk&f=39347.39348.39349&a=81954438&app=typekit&e=css
h2
960.32800001558
1039.8029999924
317
5
200
text/css
Stylesheet
https://www.womensrunning.co.uk/wp-content/themes/anthem/im/icon-arrow-up.png
h2
1046.6770000057
1069.7330000112
2209
1320
200
image/png
Image
https://www.womensrunning.co.uk/wp-content/themes/anthem/im/quicklinks-bg.png
h2
1064.3430000055
1382.5599999982
1867
981
200
image/png
Image
https://use.typekit.net/af/26a6d6/00000000000000003b9b1fb4/27/l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=n3&v=3
h2
1073.4850000008
1154.143999971
31294
30976
200
application/font-woff2
Font
https://use.typekit.net/af/f1d156/00000000000000003b9b1fb5/27/l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=n5&v=3
h2
1073.6739999847
1097.8619999951
31978
31660
200
application/font-woff2
Font
https://www.womensrunning.co.uk/wp-content/themes/anthem/im/icon-down-white.png
h2
1191.8120000046
1242.0929999789
5929
5035
200
image/png
Image
https://www.womensrunning.co.uk/wp-content/uploads/2017/08/plus-sizes-runners-beginner-tips-768x338.jpg
h2
1205.1460000221
1660.8049999923
33039
32154
200
image/jpeg
Image
https://www.womensrunning.co.uk/wp-content/uploads/2021/11/WR-2021-quicklinks-where-to-buy-414x252.jpg
h2
1205.4869999993
1590.3290000279
18246
17353
200
image/jpeg
Image
https://www.womensrunning.co.uk/wp-content/uploads/2021/11/wr-2021-quicklinks-zerofit-subs-414x252.jpg
h2
1205.8250000118
1813.564000011
38824
37937
200
image/jpeg
Image
https://www.womensrunning.co.uk/wp-content/uploads/2021/12/WR-newsletter-homepage-block-414x252.jpg
h2
1206.0400000191
1568.7819999876
15465
14570
200
image/jpeg
Image
https://www.womensrunning.co.uk/wp-content/uploads/2022/08/How-to-run-longer-distances-414x182.jpg
h2
1206.2499999884
1609.0819999808
15298
14413
200
image/jpeg
Image
https://www.womensrunning.co.uk/wp-content/uploads/2022/08/england-womens-football-team-win-euro-2022-414x182.jpg
h2
1206.474000006
1655.9899999993
20506
19627
200
image/jpeg
Image
https://www.womensrunning.co.uk/wp-content/uploads/2022/08/Featured-image-template-8-414x182.jpg
h2
1206.7369999713
1363.9349999721
12920
12026
200
image/jpeg
Image
https://www.womensrunning.co.uk/wp-content/uploads/2022/07/COMP-BANNER-768x338.png
h2
1207.5489999843
1868.6009999947
358131
357241
200
image/png
Image
https://www.womensrunning.co.uk/wp-content/themes/anthem/im/icon-toggle.png
h2
1209.1229999787
1507.2819999768
2044
1162
200
image/png
Image
https://www.womensrunning.co.uk/wp-content/themes/anthem/im/womens-running-logo.png
h2
1209.3420000165
1643.7010000227
30271
29389
200
image/png
Image
https://www.womensrunning.co.uk/wp-content/themes/anthem/im/icon-search.png
h2
1209.664999973
1804.7179999994
2518
1634
200
image/png
Image
https://www.womensrunning.co.uk/wp-content/themes/anthem/im/womens-running-logo-white.png
h2
1210.1649999968
1234.0470000054
28298
27401
200
image/png
Image
https://www.womensrunning.co.uk/wp-content/themes/anthem/im/icon-close-white.png
h2
1210.4740000213
1235.2490000194
2156
1259
200
image/png
Image
https://www.womensrunning.co.uk/wp-content/themes/anthem/im/icon-twitter-white.png
h2
1210.7139999862
1233.4569999948
3326
2434
200
image/png
Image
https://www.womensrunning.co.uk/wp-content/themes/anthem/im/pinterest-50px.png
h2
1211.025000026
1234.5559999812
1796
893
200
image/png
Image
https://www.womensrunning.co.uk/wp-content/themes/anthem/im/youtube-50px.png
h2
1211.3220000174
1260.9860000084
1390
495
200
image/png
Image
https://www.womensrunning.co.uk/wp-content/themes/anthem/im/featured-image-placeholder.png
h2
1212.2860000236
1240.8099999884
4120
3223
200
image/png
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)
919.987
12.926
933.185
9.471
946.158
5.183
1077.6
66.051
1154.429
72.099
1226.585
7.634
1237.174
9.147
1246.393
17.541
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. Womensrunning.co.uk should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images — Potential savings of 55 KiB
Images can slow down the page's load time. Womensrunning.co.uk should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.womensrunning.co.uk/wp-content/themes/anthem/im/womens-running-logo.png
29389
28966
https://www.womensrunning.co.uk/wp-content/themes/anthem/im/womens-running-logo-white.png
27401
27127
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Womensrunning.co.uk should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Womensrunning.co.uk should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Womensrunning.co.uk should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Womensrunning.co.uk should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript — Potential savings of 21 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.womensrunning.co.uk/wp-content/themes/anthem/js/jquery.min.js
35234
21625
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 470 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.womensrunning.co.uk/
473.016
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Womensrunning.co.uk 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 0 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://www.womensrunning.co.uk/
167
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 739 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.womensrunning.co.uk/wp-content/uploads/2022/07/COMP-BANNER-768x338.png
358131
https://www.womensrunning.co.uk/wp-content/uploads/2021/11/wr-2021-quicklinks-zerofit-subs-414x252.jpg
38824
https://www.womensrunning.co.uk/wp-content/themes/anthem/js/jquery.min.js
35234
https://www.womensrunning.co.uk/wp-content/uploads/2017/08/plus-sizes-runners-beginner-tips-768x338.jpg
33039
https://use.typekit.net/af/f1d156/00000000000000003b9b1fb5/27/l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=n5&v=3
31978
https://use.typekit.net/af/26a6d6/00000000000000003b9b1fb4/27/l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=n3&v=3
31294
https://www.womensrunning.co.uk/wp-content/themes/anthem/im/womens-running-logo.png
30271
https://www.womensrunning.co.uk/wp-content/themes/anthem/im/womens-running-logo-white.png
28298
https://www.womensrunning.co.uk/
21633
https://www.womensrunning.co.uk/wp-content/uploads/2022/08/england-womens-football-team-win-euro-2022-414x182.jpg
20506
Uses efficient cache policy on static assets — 1 resource found
Womensrunning.co.uk 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://p.typekit.net/p.css?s=1&k=vuo8oip&ht=tk&f=39347.39348.39349&a=81954438&app=typekit&e=css
604800000
317
Avoids an excessive DOM size — 712 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
712
Maximum DOM Depth
14
Maximum Child Elements
15
Avoid chaining critical requests — 7 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Womensrunning.co.uk 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.womensrunning.co.uk/
153.956
14.861
2.402
https://www.womensrunning.co.uk/wp-content/themes/anthem/js/jquery.min.js
68.283
48.794
1.692
Minimizes main-thread work — 0.3 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)
Style & Layout
82.919
Script Evaluation
82.76
Other
63.029
Rendering
35.758
Parse HTML & CSS
17.865
Script Parsing & Compilation
5.39
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 — 36 requests • 739 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
36
756449
Image
20
598353
Font
2
63272
Script
5
54014
Document
1
21633
Stylesheet
6
17635
Other
2
1542
Media
0
0
Third-party
3
63589
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)
63589
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
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
Avoid large layout shifts — 3 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.0015337517511601
0.00093409180457053
0.00059510988529901
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
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
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 womensrunning.co.uk 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.

Other

Serve images in next-gen formats — Potential savings of 364 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.womensrunning.co.uk/wp-content/uploads/2022/07/COMP-BANNER-768x338.png
357241
323092.45
https://www.womensrunning.co.uk/wp-content/uploads/2017/08/plus-sizes-runners-beginner-tips-768x338.jpg
32154
15190.2
https://www.womensrunning.co.uk/wp-content/uploads/2021/11/wr-2021-quicklinks-zerofit-subs-414x252.jpg
37937
11739
https://www.womensrunning.co.uk/wp-content/themes/anthem/im/womens-running-logo-white.png
27401
11623.9
https://www.womensrunning.co.uk/wp-content/themes/anthem/im/womens-running-logo.png
29389
11535.7
Avoid multiple page redirects — Potential savings of 340 ms
Redirects can cause additional delays before the page can begin loading. Womensrunning.co.uk should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://womensrunning.co.uk/
190
https://womensrunning.co.uk/
150
https://www.womensrunning.co.uk/
0

Other

Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://www.womensrunning.co.uk/wp-content/themes/anthem/im/womens-running-logo.png
95

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of womensrunning.co.uk. 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.
Links 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.
`<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"]`
Womensrunning.co.uk 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

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
10K
10K

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that womensrunning.co.uk 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.
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
No CSP found in enforcement mode
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
1.11.1
WordPress
6.0.1
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.
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://womensrunning.co.uk/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 4 vulnerabilities detected
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.
Library Version Vulnerability Count Highest Severity
4
Medium
92

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for womensrunning.co.uk. 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 womensrunning.co.uk 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.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the 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.

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

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 womensrunning.co.uk. This includes details about web app manifests.

PWA Optimized

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 womensrunning.co.uk on mobile screens.

Installable

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

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide 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.
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) 77
Performance 86
Accessibility 95
Best Practices 83
SEO 90
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.womensrunning.co.uk/
Updated: 4th August, 2022
Simulate loading on mobile
86

Performance

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

Metrics

Time to Interactive — 3.2 s
The time taken for the page to become fully interactive.
Speed Index — 3.1 s
The time taken for the page contents to be visibly populated.
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).
Cumulative Layout Shift — 0.026
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 60 ms
Users could experience a delay when interacting with the page.
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://womensrunning.co.uk/
http/1.1
0
40.559999994002
741
0
301
text/plain
https://womensrunning.co.uk/
http/1.1
40.9529999597
198.32999998471
780
0
301
text/html
https://www.womensrunning.co.uk/
h2
198.66599998204
567.00599996839
21624
127620
200
text/html
Document
https://www.womensrunning.co.uk/wp-content/cache/min/1/wp-content/themes/anthem/css/core.css?ver=1659539556
h2
578.81999999518
609.30199996801
9022
45057
200
text/css
Stylesheet
https://www.womensrunning.co.uk/wp-content/cache/min/1/wp-content/themes/anthem/css/responsive.css?ver=1659539556
h2
579.1479999898
617.56099999184
4030
13708
200
text/css
Stylesheet
https://www.womensrunning.co.uk/wp-content/cache/min/1/wp-content/themes/anthem/css/print.css?ver=1659539556
h2
579.42399999592
607.26899997098
1617
1887
200
text/css
Stylesheet
https://www.womensrunning.co.uk/wp-content/cache/min/1/vuo8oip.css?ver=1659539556
h2
579.74299998023
606.86800000258
1305
2084
200
text/css
Stylesheet
https://www.womensrunning.co.uk/wp-content/themes/anthem/js/jquery.min.js
h2
590.36899998318
629.1219999548
35222
95785
200
application/javascript
Script
https://www.womensrunning.co.uk/wp-content/cache/min/1/wp-content/themes/anthem/js/jquery.cookie.js?ver=1659539556
h2
590.6149999937
622.91799997911
1828
1921
200
application/javascript
Script
https://www.womensrunning.co.uk/wp-content/themes/anthem/js/slick.min.js
h2
590.95699997852
616.92199995741
11147
40090
200
application/javascript
Script
https://www.womensrunning.co.uk/wp-content/cache/min/1/wp-content/themes/anthem/js/slick.css?ver=1659539556
h2
580.45599999605
603.01399999298
1352
1322
200
text/css
Stylesheet
https://www.womensrunning.co.uk/wp-content/cache/min/1/wp-content/themes/anthem/js/global.js?ver=1659539556
h2
591.09699999681
624.73499996122
2001
3157
200
application/javascript
Script
https://www.womensrunning.co.uk/wp-content/plugins/wp-rocket/assets/js/lazyload/17.5/lazyload.min.js
h2
591.20699996129
631.25699997181
3814
8291
200
application/javascript
Script
data
593.38899998693
593.51799997967
0
66
200
image/svg+xml
Image
data
595.13799997512
595.25099996245
0
64
200
image/svg+xml
Image
data
599.04000000097
599.14800000843
0
69
200
image/svg+xml
Image
data
601.92099999404
602.03800001182
0
66
200
image/svg+xml
Image
data
603.62099995837
603.7270000088
0
66
200
image/svg+xml
Image
data
605.22599995602
605.33299995586
0
68
200
image/svg+xml
Image
https://p.typekit.net/p.css?s=1&k=vuo8oip&ht=tk&f=39347.39348.39349&a=81954438&app=typekit&e=css
h2
613.53599996073
695.64699998591
317
5
200
text/css
Stylesheet
data
625.44599996181
625.52599998889
0
68
200
image/svg+xml
Image
https://www.womensrunning.co.uk/wp-content/themes/anthem/im/icon-arrow-up.png
h2
701.48799999151
725.6359999883
2221
1320
200
image/png
Image
https://www.womensrunning.co.uk/wp-content/themes/anthem/im/quicklinks-bg.png
h2
706.43999997992
734.43599999882
1874
981
200
image/png
Image
https://use.typekit.net/af/26a6d6/00000000000000003b9b1fb4/27/l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=n3&v=3
h2
712.05299999565
735.40899995714
31294
30976
200
application/font-woff2
Font
https://use.typekit.net/af/f1d156/00000000000000003b9b1fb5/27/l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=n5&v=3
h2
712.23000000464
801.11000000034
31978
31660
200
application/font-woff2
Font
https://www.womensrunning.co.uk/wp-content/themes/anthem/im/icon-down-white.png
h2
797.68699995475
822.69299996551
5929
5035
200
image/png
Image
https://www.womensrunning.co.uk/wp-content/themes/anthem/im/icon-toggle.png
h2
804.08299999544
824.71499999519
2050
1162
200
image/png
Image
https://www.womensrunning.co.uk/wp-content/themes/anthem/im/womens-running-logo.png
h2
804.30299998261
830.09499998298
30283
29389
200
image/png
Image
https://www.womensrunning.co.uk/wp-content/themes/anthem/im/icon-search.png
h2
804.57999999635
1080.3319999832
2519
1634
200
image/png
Image
https://www.womensrunning.co.uk/wp-content/themes/anthem/im/womens-running-logo-white.png
h2
804.80799998622
837.20000000903
28296
27401
200
image/png
Image
https://www.womensrunning.co.uk/wp-content/themes/anthem/im/icon-close-white.png
h2
805.11899996782
825.53500001086
2154
1259
200
image/png
Image
https://www.womensrunning.co.uk/wp-content/uploads/2017/08/plus-sizes-runners-beginner-tips-768x338.jpg
h2
805.3699999582
829.00899997912
33051
32154
200
image/jpeg
Image
https://www.womensrunning.co.uk/wp-content/themes/anthem/im/featured-image-placeholder.png
h2
805.60999998124
827.91599998018
4120
3223
200
image/png
Image
https://www.womensrunning.co.uk/wp-content/uploads/2021/11/WR-2021-quicklinks-where-to-buy-414x252.jpg
h2
805.76099996688
1190.2559999726
18234
17353
200
image/jpeg
Image
https://www.womensrunning.co.uk/wp-content/uploads/2021/11/wr-2021-quicklinks-zerofit-subs-414x252.jpg
h2
806.10899999738
1003.3829999738
38820
37937
200
image/jpeg
Image
https://www.womensrunning.co.uk/wp-content/uploads/2021/12/WR-newsletter-homepage-block-414x252.jpg
h2
806.33399996441
831.49899996351
15465
14570
200
image/jpeg
Image
https://www.womensrunning.co.uk/wp-content/uploads/2022/08/How-to-run-longer-distances-414x182.jpg
h2
806.62899999879
830.49500000197
15309
14413
200
image/jpeg
Image
https://www.womensrunning.co.uk/wp-content/uploads/2022/08/england-womens-football-team-win-euro-2022-414x182.jpg
h2
806.78899999475
1163.3589999983
20523
19627
200
image/jpeg
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)
594.49
14.583
609.382
10.917
624.369
5.995
722.067
44.614
772.64
15.294
790.938
31.965
825.012
6.935
834.42
16.3
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. Womensrunning.co.uk should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Womensrunning.co.uk should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Womensrunning.co.uk should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Womensrunning.co.uk should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Womensrunning.co.uk should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 370 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.womensrunning.co.uk/
369.334
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Womensrunning.co.uk 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 0 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://www.womensrunning.co.uk/
167
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 370 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.womensrunning.co.uk/wp-content/uploads/2021/11/wr-2021-quicklinks-zerofit-subs-414x252.jpg
38820
https://www.womensrunning.co.uk/wp-content/themes/anthem/js/jquery.min.js
35222
https://www.womensrunning.co.uk/wp-content/uploads/2017/08/plus-sizes-runners-beginner-tips-768x338.jpg
33051
https://use.typekit.net/af/f1d156/00000000000000003b9b1fb5/27/l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=n5&v=3
31978
https://use.typekit.net/af/26a6d6/00000000000000003b9b1fb4/27/l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=n3&v=3
31294
https://www.womensrunning.co.uk/wp-content/themes/anthem/im/womens-running-logo.png
30283
https://www.womensrunning.co.uk/wp-content/themes/anthem/im/womens-running-logo-white.png
28296
https://www.womensrunning.co.uk/
21624
https://www.womensrunning.co.uk/wp-content/uploads/2022/08/england-womens-football-team-win-euro-2022-414x182.jpg
20523
https://www.womensrunning.co.uk/wp-content/uploads/2021/11/WR-2021-quicklinks-where-to-buy-414x252.jpg
18234
Uses efficient cache policy on static assets — 1 resource found
Womensrunning.co.uk 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://p.typekit.net/p.css?s=1&k=vuo8oip&ht=tk&f=39347.39348.39349&a=81954438&app=typekit&e=css
604800000
317
Avoids an excessive DOM size — 712 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
712
Maximum DOM Depth
14
Maximum Child Elements
15
Avoid chaining critical requests — 7 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Womensrunning.co.uk 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.2 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.womensrunning.co.uk/
546.412
65.192
11.512
Unattributable
118.44
12.02
0.656
https://www.womensrunning.co.uk/wp-content/themes/anthem/js/jquery.min.js
112.944
92.188
6.984
https://www.womensrunning.co.uk/wp-content/plugins/wp-rocket/assets/js/lazyload/17.5/lazyload.min.js
52.184
44.916
1.072
Minimizes main-thread work — 0.9 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)
Style & Layout
236.492
Script Evaluation
217.916
Other
210.092
Rendering
107.632
Parse HTML & CSS
73.732
Script Parsing & Compilation
23.436
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 — 31 requests • 370 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
31
378920
Image
15
220848
Font
2
63272
Script
5
54012
Document
1
21624
Stylesheet
6
17643
Other
2
1521
Media
0
0
Third-party
3
63589
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)
63589
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
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
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.014324520275157
0.0070271231538506
0.0037838355443811
0.00030069665594415
0.00029951745337182
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 — 3 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://www.womensrunning.co.uk/
2120
89
https://www.womensrunning.co.uk/wp-content/themes/anthem/js/jquery.min.js
3240
64
https://www.womensrunning.co.uk/
2040
58
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
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 womensrunning.co.uk 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

Largest Contentful Paint — 3.3 s
The timing of the largest text or image that is painted.

Audits

First Meaningful Paint — 3.1 s
The time taken for the primary content of the page to be rendered.

Other

Properly size images — Potential savings of 51 KiB
Images can slow down the page's load time. Womensrunning.co.uk should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.womensrunning.co.uk/wp-content/themes/anthem/im/womens-running-logo.png
29389
26473
https://www.womensrunning.co.uk/wp-content/themes/anthem/im/womens-running-logo-white.png
27401
25513
Reduce unused JavaScript — Potential savings of 21 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.womensrunning.co.uk/wp-content/themes/anthem/js/jquery.min.js
35222
21617
Serve images in next-gen formats — Potential savings of 49 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.womensrunning.co.uk/wp-content/uploads/2017/08/plus-sizes-runners-beginner-tips-768x338.jpg
32154
15190.2
https://www.womensrunning.co.uk/wp-content/uploads/2021/11/wr-2021-quicklinks-zerofit-subs-414x252.jpg
37937
11739
https://www.womensrunning.co.uk/wp-content/themes/anthem/im/womens-running-logo-white.png
27401
11623.9
https://www.womensrunning.co.uk/wp-content/themes/anthem/im/womens-running-logo.png
29389
11535.7

Metrics

First Contentful Paint — 3.1 s
The time taken for the first image or text on the page to be rendered.

Other

Avoid multiple page redirects — Potential savings of 1,110 ms
Redirects can cause additional delays before the page can begin loading. Womensrunning.co.uk should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://womensrunning.co.uk/
630
https://womensrunning.co.uk/
480
https://www.womensrunning.co.uk/
0
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://www.womensrunning.co.uk/wp-content/themes/anthem/im/womens-running-logo.png
First Contentful Paint (3G) — 6120 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
95

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of womensrunning.co.uk. 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.
Links 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.
`<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"]`
Womensrunning.co.uk 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

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
10K
10K

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that womensrunning.co.uk 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.
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
No CSP found in enforcement mode
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
1.11.1
WordPress
6.0.1
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.
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://womensrunning.co.uk/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 4 vulnerabilities detected
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.
Library Version Vulnerability Count Highest Severity
4
Medium
90

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for womensrunning.co.uk. 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 womensrunning.co.uk 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

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.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the 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.

Mobile Friendly

Tap targets are not sized appropriately — 63% 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.
Tap Target Size Overlapping Target
165x14
165x14
165x14
165x14
165x14
165x14
165x14
10K
165x14
165x14
165x14
165x14
165x14
165x14
165x14
330x14
340x14
340x14
340x14
10K
340x14
165x14
165x14
165x14
165x14
165x14
25x29
150x29
150x29
150x29
150x29

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

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 womensrunning.co.uk. This includes details about web app manifests.

PWA Optimized

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 womensrunning.co.uk on mobile screens.

Installable

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

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide 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.
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: 172.67.181.80
Continent: North America
Country: United States
United States Flag
Region:
City:
Longitude: -97.822
Latitude: 37.751
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Cloudflare, Inc.
Registration

Domain Registrant

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

Domain Registrar

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: *.womensrunning.co.uk
Issued By: E1
Valid From: 27th June, 2022
Valid To: 25th September, 2022
Subject: CN = *.womensrunning.co.uk
Hash: aa7ee621
Issuer: CN = E1
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x03155259D81124DAEE7D7125B3E006164DB7
Serial Number (Hex): 03155259D81124DAEE7D7125B3E006164DB7
Valid From: 27th June, 2024
Valid To: 25th September, 2024
Signature Algorithm (Short Name): ecdsa-with-SHA384
Signature Algorithm (Long Name): ecdsa-with-SHA384
Authority Key Identifier: keyid:5A:F3:ED:2B:FC:36:C2:37:79:B9:52:30:EA:54:6F:CF:55:CB:2E:AC
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://e1.o.lencr.org
CA Issuers - URI:http://e1.i.lencr.org/

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 41:C8:CA:B1:DF:22:46:4A:10:C6:A1:3A:09:42:87:5E:
4E:31:8B:1B:03:EB:EB:4B:C7:68:F0:90:62:96:06:F6
Timestamp : Jun 27 10:07:47.047 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:C2:A5:2A:FE:3E:1F:2D:E5:6F:73:5C:
7B:04:07:C2:09:FD:2E:89:59:D4:89:A5:BF:72:56:7A:
C6:76:77:F5:8E:02:21:00:CC:12:41:98:18:2E:3D:7C:
5B:CD:D0:37:FA:2A:48:83:65:FA:A2:21:E6:99:F9:47:
8E:55:1E:1F:C6:40:7E:A0
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 46:A5:55:EB:75:FA:91:20:30:B5:A2:89:69:F4:F3:7D:
11:2C:41:74:BE:FD:49:B8:85:AB:F2:FC:70:FE:6D:47
Timestamp : Jun 27 10:07:47.059 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:A7:24:25:C7:BA:40:FE:31:82:AE:26:
D7:6E:87:CD:39:05:96:97:4E:3B:72:B3:56:08:FD:C3:
5B:CC:2E:4A:6B:02:20:0E:74:B5:D4:51:03:79:23:BD:
BA:74:CE:FC:05:FB:0B:45:E9:99:45:BC:E8:CC:1B:E3:
D9:A1:2C:6A:D0:68:24
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:womensrunning.co.uk
DNS:*.womensrunning.co.uk
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 301 Moved Permanently
Date: 4th August, 2022
Content-Type: text/html
Server: cloudflare
Connection: keep-alive
location: https://www.womensrunning.co.uk/
CF-Cache-Status: DYNAMIC
Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=EpUbMFZDsUPdE3gkKVVIrN9JHpHZrbb200DZnF6Kc%2Bht7Gg33M5QEm0weTi7%2FBcryc99asWknec9ywPPQBTfK2sRA%2BICKfsC4Kxhe4Q6V9ZC9yBvIz6q7opImnQt%2Fd4K0yyt3zhP"}],"group":"cf-nel","max_age":604800}
NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
CF-RAY: 7356e2280e233354-EWR
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400

Whois Lookup

Created: 29th November, 2012
Changed: 27th June, 2022
Expires: 29th November, 2023
Registrar: 123-Reg Limited t/a 123-reg [Tag = 123-REG]
Status:
Nameservers: henry.ns.cloudflare.com
romina.ns.cloudflare.com
Owner Organization: Anthem Publishing Ltd
Full Whois:
Domain name:
womensrunning.co.uk

Registrant:
Anthem Publishing Ltd

Registrant type:
UK Limited Company, (Company number: 4542063)

Registrant's address:
Suite 6 Piccadilly House
London Road
Bath
BA1 6PL
United Kingdom

Data validation:
Nominet was able to match the registrant's name and address against a 3rd party data source on 20-Aug-2019

Registrar:
123-Reg Limited t/a 123-reg [Tag = 123-REG]
URL: https://www.123-reg.co.uk

Relevant dates:
Registered on: 29-Nov-2012
Expiry date: 29-Nov-2023
Last updated: 27-Jun-2022

Registration status:
Registered until expiry date.

Name servers:
henry.ns.cloudflare.com
romina.ns.cloudflare.com

WHOIS lookup made at 12:16:55 04-Aug-2022

--
This WHOIS information is provided for free by Nominet UK the central registry
for .uk domain names. This information and the .uk WHOIS are:

Copyright Nominet UK 1996 - 2022.

You may not access the .uk WHOIS or use any data from it except as permitted
by the terms of use available in full at https://www.nominet.uk/whoisterms,
which includes restrictions on: (A) use of the data for advertising, or its
repackaging, recompilation, redistribution or reuse (B) obscuring, removing
or hiding any or all of this notice and (C) exceeding query rate or volume
limits. The data is provided on an 'as-is' basis and may lag behind the
register. Access may be withdrawn or restricted at any time.

Nameservers

Name IP Address
henry.ns.cloudflare.com 108.162.193.176
romina.ns.cloudflare.com 162.159.38.159
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
$4,129 USD 3/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
0/5
0/5