myrunningman.com

myrunningman.com is SSL secured

Free website and domain report on myrunningman.com

Last Updated: 15th May, 2023 Update Now
Overview

Snoop Summary for myrunningman.com

This is a free and comprehensive report about myrunningman.com. Our records indicate that myrunningman.com is privately registered by DATA REDACTED. Myrunningman.com is expected to earn an estimated $19 USD per day from advertising revenue. The sale of myrunningman.com would possibly be worth $14,182 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Myrunningman.com is very popular with an estimated 6,812 daily unique visitors. This report was last updated 15th May, 2023.

About myrunningman.com

Site Preview: myrunningman.com myrunningman.com
Title: Home - My Running Man (MyRM)
Description: Your personalized Running Man (런닝맨) experience where you can stream and watch all episodes online for free.
Keywords and Tags: online shopping
Related Terms: kshowonline running man, running man, running man 161 vietsub, running man eng sub, running man episode kshowonline, running man kshow, running man vietsub, smallencode running man, vietsub running man
Fav Icon:
Age: Over 7 years old
Domain Created: 12th September, 2016
Domain Updated: 20th August, 2022
Domain Expires: 12th September, 2023
Review

Snoop Score

2/5

Valuation

$14,182 USD
Note: All valuation figures are estimates.

Popularity

High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 64,937
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 22
Moz Page Authority: 40

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 6,812
Monthly Visitors: 207,336
Yearly Visitors: 2,486,380
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $19 USD
Monthly Revenue: $591 USD
Yearly Revenue: $7,086 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: myrunningman.com 16
Domain Name: myrunningman 12
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 77
Performance 94
Accessibility 86
Best Practices 80
SEO 90
Progressive Web App 36
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.myrunningman.com/
Updated: 19th October, 2021

1.92 seconds
First Contentful Paint (FCP)
72%
17%
11%

0.00 seconds
First Input Delay (FID)
99%
0%
1%

Simulate loading on desktop
94

Performance

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

Metrics

First Contentful Paint — 0.8 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 0.9 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 0.8 s
The timing of the largest text or image that is painted.
Time to Interactive — 1.1 s
The time taken for the page to become fully interactive.
Total Blocking Time — 40 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).

Other

Max Potential First Input Delay — 120 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://myrunningman.com/
http/1.1
0
105.93999992125
769
0
301
text/html
https://www.myrunningman.com/
h2
106.84999986552
309.59700001404
9618
67924
200
text/html
Document
https://www.myrunningman.com/assets/css/bootstrap.min.3.css
h2
335.8719998505
423.84199984372
21556
123575
200
text/css
Stylesheet
https://cdn.jsdelivr.net/npm/fork-awesome@1.1.5/css/fork-awesome.min.css
h2
336.4780000411
361.74699990079
9146
34561
200
text/css
Stylesheet
https://www.myrunningman.com/assets/css/jquery-ui.min.css
h2
336.71499998309
424.51200005598
3748
15762
200
text/css
Stylesheet
https://www.myrunningman.com/assets/css/jquery.qtip.min.css
h2
336.95299993269
357.76999988593
2643
7491
200
text/css
Stylesheet
https://www.myrunningman.com/assets/img/fist.png
h2
340.17099998891
429.36499998905
28461
27592
200
image/png
Image
https://www.myrunningman.com/assets/epimg/575_temp.jpg
h2
340.45200003311
480.61900003813
13838
12973
200
image/jpeg
Image
https://www.myrunningman.com/assets/epimg/574_temp.jpg
h2
341.00999985822
427.99400002696
13000
12125
200
image/jpeg
Image
https://www.myrunningman.com/assets/epimg/573_temp.jpg
h2
341.36600000784
387.08100002259
14367
13493
200
image/jpeg
Image
https://www.myrunningman.com/assets/epimg/572_temp.jpg
h2
341.61600004882
390.67599992268
11402
10530
200
image/jpeg
Image
https://www.myrunningman.com/assets/epimg/001.jpg
h2
341.86699986458
360.31599994749
14756
13885
200
image/jpeg
Image
https://www.myrunningman.com/assets/epimg/002.jpg
h2
342.04200003296
391.72800001688
16324
15451
200
image/jpeg
Image
https://www.myrunningman.com/assets/epimg/003.jpg
h2
342.30599994771
428.86999994516
13820
12946
200
image/jpeg
Image
https://www.myrunningman.com/assets/epimg/004.jpg
h2
344.25299987197
417.53500001505
17329
16453
200
image/jpeg
Image
https://www.myrunningman.com/assets/epimg/074.jpg
h2
345.19000002183
419.74299983121
13345
12471
200
image/jpeg
Image
https://www.myrunningman.com/assets/epimg/162.jpg
h2
345.37100000307
474.82299990952
20290
19415
200
image/jpeg
Image
https://www.myrunningman.com/assets/epimg/178.jpg
h2
345.62799986452
387.65899999999
16810
15932
200
image/jpeg
Image
https://www.myrunningman.com/assets/epimg/091.jpg
h2
345.86100000888
438.85999987833
9670
8797
200
image/jpeg
Image
https://www.myrunningman.com/assets/css/myrunningman4.css
h2
346.05799987912
415.68999993615
1689
2109
200
text/css
Stylesheet
https://www.myrunningman.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js
h2
346.18799993768
418.04399993271
4708
12332
200
application/javascript
Script
https://www.myrunningman.com/assets/css/lato.css
h2
467.96999988146
543.29099995084
1332
1616
200
text/css
Stylesheet
https://cdn.jsdelivr.net/npm/fork-awesome@1.1.5/fonts/forkawesome-webfont.woff2?v=1.1.5
h2
500.78899995424
515.69400005974
91333
90420
200
font/woff2
Font
https://myrunningman.disqus.com/count.js
http/1.1
628.90199990943
684.4089999795
1584
1517
200
application/javascript
Script
https://www.myrunningman.com/assets/js/myrunningman41.js
h2
629.49700001627
658.79799984396
4184
10083
200
application/javascript
Script
https://www.myrunningman.com/assets/js/jquery.qtip.min.js
h2
629.66499989852
654.94799986482
13840
34363
200
application/javascript
Script
https://www.myrunningman.com/assets/js/stupidtable.min.js
h2
629.94599994272
704.0229998529
1612
1750
200
application/javascript
Script
https://www.myrunningman.com/assets/js/jquery-ui.min.js
h2
630.63899986446
673.32399985753
11252
32162
200
application/javascript
Script
https://www.myrunningman.com/assets/js/bootstrap.min.js
h2
630.95899997279
714.24299990758
11127
37045
200
application/javascript
Script
https://www.myrunningman.com/assets/js/jquery.min.js
h2
631.3300000038
663.6840000283
36362
98830
200
application/javascript
Script
https://www.myrunningman.com/assets/fonts/1YwB1sO8YE1Lyjf12WNiUA.woff2
h2
638.5790000204
680.30899995938
24205
23316
200
application/octet-stream
Font
https://www.myrunningman.com/assets/fonts/H2DMvhDLycM56KNuAtbJYA.woff2
h2
647.31699996628
676.99999990873
23703
22820
200
application/octet-stream
Font
https://www.google-analytics.com/analytics.js
h2
925.07599992678
952.56899995729
20399
49529
200
text/javascript
Script
https://myrunningman.disqus.com/count-data.js?2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F1&2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F162&2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F178&2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F2&2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F3&2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F4&2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F572&2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F573&2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F574&2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F575
http/1.1
1129.5739999041
1178.5849998705
1384
803
200
application/javascript
Script
https://myrunningman.disqus.com/count-data.js?2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F74&2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F91
http/1.1
1129.8630000092
1164.1090000048
889
308
200
application/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j93&a=524855262&t=pageview&_s=1&dl=https%3A%2F%2Fwww.myrunningman.com%2F&ul=en-us&de=UTF-8&dt=Home%20-%20My%20Running%20Man%20(MyRM)&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAEABAAAAAC~&jid=420661697&gjid=1087897485&cid=413571604.1634654009&tid=UA-84235540-1&_gid=1760431413.1634654009&_r=1&_slc=1&z=375166787
h2
1181.0250000563
1186.8989998475
646
2
200
text/plain
XHR
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)
353.174
12.038
366.474
5.6
373.085
7.503
465.311
8.041
474.654
9.861
490.727
13.963
505.989
129.113
638.243
14.539
652.85
54.546
707.51
79.454
794.18
53.506
850.46
19.336
870.976
25.737
897.27
8.379
906.099
6.24
913.483
5.649
919.148
233.781
1153.111
7.911
1161.117
6.128
1168.289
6.782
1176.386
43.757
1224.79
10.908
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

Properly size images — Potential savings of 31 KiB
Images can slow down the page's load time. Myrunningman.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.myrunningman.com/assets/img/fist.png
27592
27568
https://www.myrunningman.com/assets/epimg/162.jpg
19415
4522
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Myrunningman.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Myrunningman.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Myrunningman.com should consider minifying JS files.
Reduce unused CSS — Potential savings of 19 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Myrunningman.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.myrunningman.com/assets/css/bootstrap.min.3.css
21556
19674
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 — Potential savings of 12 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.myrunningman.com/assets/img/fist.png
27592
11988.55
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.myrunningman.com/
203.737
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Myrunningman.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://myrunningman.com/
190
https://www.myrunningman.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Myrunningman.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
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.
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 489 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://cdn.jsdelivr.net/npm/fork-awesome@1.1.5/fonts/forkawesome-webfont.woff2?v=1.1.5
91333
https://www.myrunningman.com/assets/js/jquery.min.js
36362
https://www.myrunningman.com/assets/img/fist.png
28461
https://www.myrunningman.com/assets/fonts/1YwB1sO8YE1Lyjf12WNiUA.woff2
24205
https://www.myrunningman.com/assets/fonts/H2DMvhDLycM56KNuAtbJYA.woff2
23703
https://www.myrunningman.com/assets/css/bootstrap.min.3.css
21556
https://www.google-analytics.com/analytics.js
20399
https://www.myrunningman.com/assets/epimg/162.jpg
20290
https://www.myrunningman.com/assets/epimg/004.jpg
17329
https://www.myrunningman.com/assets/epimg/178.jpg
16810
Uses efficient cache policy on static assets — 5 resources found
Myrunningman.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://myrunningman.disqus.com/count.js
300000
1584
https://myrunningman.disqus.com/count-data.js?2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F1&2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F162&2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F178&2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F2&2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F3&2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F4&2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F572&2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F573&2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F574&2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F575
600000
1384
https://myrunningman.disqus.com/count-data.js?2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F74&2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F91
600000
889
https://www.google-analytics.com/analytics.js
7200000
20399
https://www.myrunningman.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js
172800000
4708
Avoid chaining critical requests — 6 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Myrunningman.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.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.myrunningman.com/
377.251
6.952
2.058
https://www.myrunningman.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js
222.784
212.57
1.909
Unattributable
74.152
5.414
0.43
Minimizes main-thread work — 0.8 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
324.271
Style & Layout
282.315
Other
93.848
Rendering
74.636
Parse HTML & CSS
32.586
Script Parsing & Compilation
11.082
Garbage Collection
6.708
Keep request counts low and transfer sizes small — 36 requests • 489 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
501141
Image
13
203412
Font
3
139241
Script
11
107341
Stylesheet
6
40114
Document
1
9618
Other
2
1415
Media
0
0
Third-party
7
125381
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)
100479
0
21045
0
3857
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.12055901568136
0.017183331972297
0.016346951085198
0.0040754171680548
0.0040754171680548
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.myrunningman.com/assets/js/myrunningman41.js
1101
117
https://www.myrunningman.com/
445
65
https://www.myrunningman.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js
940
55
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 myrunningman.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

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

Opportunities

Eliminate render-blocking resources — Potential savings of 340 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Myrunningman.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.myrunningman.com/assets/css/bootstrap.min.3.css
21556
80
https://cdn.jsdelivr.net/npm/fork-awesome@1.1.5/css/fork-awesome.min.css
9146
230

Diagnostics

Avoid an excessive DOM size — 1,514 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
1514
Maximum DOM Depth
11
Maximum Child Elements
576
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://cdn.jsdelivr.net/npm/fork-awesome@1.1.5/fonts/forkawesome-webfont.woff2?v=1.1.5
14.9050001055
https://www.myrunningman.com/assets/fonts/1YwB1sO8YE1Lyjf12WNiUA.woff2
41.72999993898
https://www.myrunningman.com/assets/fonts/H2DMvhDLycM56KNuAtbJYA.woff2
29.682999942452
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 Failing Elements
https://www.myrunningman.com/assets/img/fist.png
https://www.myrunningman.com/assets/epimg/575_temp.jpg
https://www.myrunningman.com/assets/epimg/574_temp.jpg
https://www.myrunningman.com/assets/epimg/573_temp.jpg
https://www.myrunningman.com/assets/epimg/572_temp.jpg
https://www.myrunningman.com/assets/epimg/001.jpg
https://www.myrunningman.com/assets/epimg/002.jpg
https://www.myrunningman.com/assets/epimg/003.jpg
https://www.myrunningman.com/assets/epimg/004.jpg
https://www.myrunningman.com/assets/epimg/074.jpg
https://www.myrunningman.com/assets/epimg/162.jpg
https://www.myrunningman.com/assets/epimg/178.jpg
https://www.myrunningman.com/assets/epimg/091.jpg
86

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of myrunningman.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.
`<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"]`
Myrunningman.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
24
17
17
19
48
11
16
28
16
any

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that myrunningman.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.
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

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
Bootstrap
3.3.7
jQuery
1.12.4
jQuery UI
1.12.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.
URL Map URL
https://www.myrunningman.com/assets/js/jquery.qtip.min.js
https://www.myrunningman.com/assets/js/jquery.qtip.min.map
https://www.myrunningman.com/assets/js/jquery.min.js
https://www.myrunningman.com/assets/js/js.cookie.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://myrunningman.com/
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Includes front-end JavaScript libraries with known security vulnerabilities — 9 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
5
Medium
4
Medium
90

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for myrunningman.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 myrunningman.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.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

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

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

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

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of myrunningman.com 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) 70
Performance 70
Accessibility 86
Best Practices 73
SEO 77
Progressive Web App 42
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.myrunningman.com/
Updated: 19th October, 2021

2.37 seconds
First Contentful Paint (FCP)
59%
28%
13%

0.02 seconds
First Input Delay (FID)
97%
2%
1%

Simulate loading on mobile
70

Performance

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

Metrics

Speed Index — 2.8 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 200 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Opportunities

Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Myrunningman.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Myrunningman.com should consider minifying JS 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 — Potential savings of 12 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.myrunningman.com/assets/img/fist.png
27592
11988.55
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 120 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.myrunningman.com/
120.026
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Myrunningman.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://myrunningman.com/
630
https://www.myrunningman.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Myrunningman.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
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.
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 489 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://cdn.jsdelivr.net/npm/fork-awesome@1.1.5/fonts/forkawesome-webfont.woff2?v=1.1.5
91331
https://www.myrunningman.com/assets/js/jquery.min.js
36359
https://www.myrunningman.com/assets/img/fist.png
28460
https://www.myrunningman.com/assets/fonts/1YwB1sO8YE1Lyjf12WNiUA.woff2
24196
https://www.myrunningman.com/assets/fonts/H2DMvhDLycM56KNuAtbJYA.woff2
23701
https://www.myrunningman.com/assets/css/bootstrap.min.3.css
21554
https://www.google-analytics.com/analytics.js
20337
https://www.myrunningman.com/assets/epimg/162.jpg
20283
https://www.myrunningman.com/assets/epimg/004.jpg
17325
https://www.myrunningman.com/assets/epimg/178.jpg
16804
Uses efficient cache policy on static assets — 5 resources found
Myrunningman.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://myrunningman.disqus.com/count.js
300000
1584
https://myrunningman.disqus.com/count-data.js?2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F1&2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F162&2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F178&2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F2&2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F3&2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F4&2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F572&2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F573&2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F574&2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F575
600000
1386
https://myrunningman.disqus.com/count-data.js?2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F74&2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F91
600000
891
https://www.google-analytics.com/analytics.js
7200000
20337
https://www.myrunningman.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js
172800000
4706
Avoid chaining critical requests — 6 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Myrunningman.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.6 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.myrunningman.com/
797.7
14.908
4.224
https://www.myrunningman.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js
409.284
392.648
2.096
Unattributable
169.024
10.096
0.572
https://www.google-analytics.com/analytics.js
100.468
90.344
3.836
https://www.myrunningman.com/assets/js/jquery.min.js
65.796
53.376
7.572
Minimizes main-thread work — 1.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
636.152
Style & Layout
574.888
Other
236.356
Rendering
125.94
Parse HTML & CSS
82.98
Script Parsing & Compilation
30.408
Garbage Collection
6.396
Keep request counts low and transfer sizes small — 36 requests • 489 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
500922
Image
13
203400
Font
3
139228
Script
11
107255
Stylesheet
6
40098
Document
1
9612
Other
2
1329
Media
0
0
Third-party
7
125258
Minimize third-party usage — Third-party code blocked the main thread for 40 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)
20921
36.688
100476
0
3861
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.2618505859375
0.115625
0.012186573028564
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 — 7 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.myrunningman.com/assets/js/myrunningman41.js
5054
192
https://www.myrunningman.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js
4110
127
https://www.myrunningman.com/
1437
124
https://www.google-analytics.com/analytics.js
6176
94
https://www.myrunningman.com/
630
75
https://www.myrunningman.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js
4237
70
https://www.myrunningman.com/assets/js/jquery.min.js
4987
67
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 myrunningman.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.

Other

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://myrunningman.com/
http/1.1
0
111.84299993329
745
0
301
text/html
https://www.myrunningman.com/
h2
112.310999888
231.34199995548
9612
67924
200
text/html
Document
https://www.myrunningman.com/assets/css/bootstrap.min.3.css
h2
246.26699998043
343.54399994481
21554
123575
200
text/css
Stylesheet
https://cdn.jsdelivr.net/npm/fork-awesome@1.1.5/css/fork-awesome.min.css
h2
246.43599998672
271.72299998347
9145
34561
200
text/css
Stylesheet
https://www.myrunningman.com/assets/css/jquery-ui.min.css
h2
246.59399990924
330.67199995276
3743
15762
200
text/css
Stylesheet
https://www.myrunningman.com/assets/css/jquery.qtip.min.css
h2
246.79299991112
303.27699996997
2643
7491
200
text/css
Stylesheet
https://www.myrunningman.com/assets/img/fist.png
h2
248.43499995768
336.97499998379
28460
27592
200
image/png
Image
https://www.myrunningman.com/assets/epimg/575_temp.jpg
h2
248.56799992267
327.99599994905
13846
12973
200
image/jpeg
Image
https://www.myrunningman.com/assets/epimg/574_temp.jpg
h2
248.95999999717
331.39599999413
12998
12125
200
image/jpeg
Image
https://www.myrunningman.com/assets/epimg/573_temp.jpg
h2
249.12599998061
327.60599988978
14361
13493
200
image/jpeg
Image
https://www.myrunningman.com/assets/epimg/572_temp.jpg
h2
249.23299998045
315.19399990793
11402
10530
200
image/jpeg
Image
https://www.myrunningman.com/assets/epimg/001.jpg
h2
249.30899997707
325.30299993232
14757
13885
200
image/jpeg
Image
https://www.myrunningman.com/assets/epimg/002.jpg
h2
249.87699999474
305.33799994737
16330
15451
200
image/jpeg
Image
https://www.myrunningman.com/assets/epimg/003.jpg
h2
250.92499994207
327.17899989802
13818
12946
200
image/jpeg
Image
https://www.myrunningman.com/assets/epimg/004.jpg
h2
251.04099989403
308.92599991057
17325
16453
200
image/jpeg
Image
https://www.myrunningman.com/assets/epimg/074.jpg
h2
251.17399997544
292.32199990656
13345
12471
200
image/jpeg
Image
https://www.myrunningman.com/assets/epimg/162.jpg
h2
251.63600000087
319.14799998049
20283
19415
200
image/jpeg
Image
https://www.myrunningman.com/assets/epimg/178.jpg
h2
251.79299991578
316.59899989609
16804
15932
200
image/jpeg
Image
https://www.myrunningman.com/assets/epimg/091.jpg
h2
251.9429998938
345.03099997528
9671
8797
200
image/jpeg
Image
https://www.myrunningman.com/assets/css/myrunningman4.css
h2
252.05299991649
280.0199999474
1685
2109
200
text/css
Stylesheet
https://www.myrunningman.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js
h2
252.1579999011
318.77799995709
4706
12332
200
application/javascript
Script
https://www.myrunningman.com/assets/css/lato.css
h2
363.31599997357
399.70999991056
1328
1616
200
text/css
Stylesheet
https://cdn.jsdelivr.net/npm/fork-awesome@1.1.5/fonts/forkawesome-webfont.woff2?v=1.1.5
h2
376.79599993862
403.74999993946
91331
90420
200
font/woff2
Font
https://myrunningman.disqus.com/count.js
http/1.1
433.77599993255
585.70999989752
1584
1517
200
application/javascript
Script
https://www.myrunningman.com/assets/js/myrunningman41.js
h2
434.2019999167
460.74499993119
4179
10083
200
application/javascript
Script
https://www.myrunningman.com/assets/js/jquery.qtip.min.js
h2
434.71599998884
461.28199994564
13833
34363
200
application/javascript
Script
https://www.myrunningman.com/assets/js/stupidtable.min.js
h2
435.21899997722
457.21799996682
1608
1750
200
application/javascript
Script
https://www.myrunningman.com/assets/js/jquery-ui.min.js
h2
435.6699999189
467.06399996765
11252
32162
200
application/javascript
Script
https://www.myrunningman.com/assets/js/bootstrap.min.js
h2
436.27999990713
484.64999999851
11120
37045
200
application/javascript
Script
https://www.myrunningman.com/assets/js/jquery.min.js
h2
437.34399997629
466.07999992557
36359
98830
200
application/javascript
Script
https://www.myrunningman.com/assets/fonts/1YwB1sO8YE1Lyjf12WNiUA.woff2
h2
440.94199989922
496.81699997745
24196
23316
200
application/octet-stream
Font
https://www.myrunningman.com/assets/fonts/H2DMvhDLycM56KNuAtbJYA.woff2
h2
445.75299997814
471.95399994962
23701
22820
200
application/octet-stream
Font
https://www.google-analytics.com/analytics.js
h2
598.74899999704
602.90299996268
20337
49529
200
text/javascript
Script
https://myrunningman.disqus.com/count-data.js?2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F1&2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F162&2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F178&2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F2&2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F3&2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F4&2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F572&2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F573&2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F574&2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F575
http/1.1
691.72199990135
802.37999989185
1386
803
200
application/javascript
Script
https://myrunningman.disqus.com/count-data.js?2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F74&2=https%3A%2F%2Fwww.myrunningman.com%2Fep%2F91
http/1.1
691.94099993911
772.65299996361
891
308
200
application/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j93&a=1615932239&t=pageview&_s=1&dl=https%3A%2F%2Fwww.myrunningman.com%2F&ul=en-us&de=UTF-8&dt=Home%20-%20My%20Running%20Man%20(MyRM)&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=IEBAAEABAAAAAC~&jid=95313539&gjid=619853954&cid=1808964402.1634654029&tid=UA-84235540-1&_gid=745315037.1634654029&_r=1&_slc=1&z=325148465
h2
716.04999992996
719.19499989599
584
2
200
text/plain
XHR
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)
266.339
7.191
387.289
8.579
395.926
62.17
460.015
31.803
491.863
37.501
529.381
7.539
542.692
34.825
577.58
9.204
587.862
16.857
606.604
6.1
622.156
96.066
725.529
23.456
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.

Metrics

First Contentful Paint — 2.8 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 3.4 s
The timing of the largest text or image that is painted.
Time to Interactive — 5.6 s
The time taken for the page to become fully interactive.

Other

Max Potential First Input Delay — 190 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 3.2 s
The time taken for the primary content of the page to be rendered.

Opportunities

Properly size images — Potential savings of 27 KiB
Images can slow down the page's load time. Myrunningman.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.myrunningman.com/assets/img/fist.png
27592
27429
Defer offscreen images — Potential savings of 113 KiB
Time to Interactive can be slowed down by resources on the page. Myrunningman.com should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.myrunningman.com/assets/epimg/162.jpg
19415
19415
https://www.myrunningman.com/assets/epimg/004.jpg
16453
16453
https://www.myrunningman.com/assets/epimg/178.jpg
15932
15932
https://www.myrunningman.com/assets/epimg/002.jpg
15451
15451
https://www.myrunningman.com/assets/epimg/001.jpg
13885
13885
https://www.myrunningman.com/assets/epimg/003.jpg
12946
12946
https://www.myrunningman.com/assets/epimg/074.jpg
12471
12471
https://www.myrunningman.com/assets/epimg/091.jpg
8797
8797
Reduce unused CSS — Potential savings of 20 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Myrunningman.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.myrunningman.com/assets/css/bootstrap.min.3.css
21554
20080

Metrics

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

Opportunities

Eliminate render-blocking resources — Potential savings of 1,350 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Myrunningman.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.myrunningman.com/assets/css/bootstrap.min.3.css
21554
300
https://cdn.jsdelivr.net/npm/fork-awesome@1.1.5/css/fork-awesome.min.css
9145
780
https://www.myrunningman.com/assets/css/jquery-ui.min.css
3743
150

Diagnostics

Avoid an excessive DOM size — 1,514 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
1514
Maximum DOM Depth
11
Maximum Child Elements
576
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://cdn.jsdelivr.net/npm/fork-awesome@1.1.5/fonts/forkawesome-webfont.woff2?v=1.1.5
26.954000000842
https://www.myrunningman.com/assets/fonts/1YwB1sO8YE1Lyjf12WNiUA.woff2
55.875000078231
https://www.myrunningman.com/assets/fonts/H2DMvhDLycM56KNuAtbJYA.woff2
26.200999971479
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 Failing Elements
https://www.myrunningman.com/assets/img/fist.png
https://www.myrunningman.com/assets/epimg/575_temp.jpg
https://www.myrunningman.com/assets/epimg/574_temp.jpg
https://www.myrunningman.com/assets/epimg/573_temp.jpg
https://www.myrunningman.com/assets/epimg/572_temp.jpg
https://www.myrunningman.com/assets/epimg/001.jpg
https://www.myrunningman.com/assets/epimg/002.jpg
https://www.myrunningman.com/assets/epimg/003.jpg
https://www.myrunningman.com/assets/epimg/004.jpg
https://www.myrunningman.com/assets/epimg/074.jpg
https://www.myrunningman.com/assets/epimg/162.jpg
https://www.myrunningman.com/assets/epimg/178.jpg
https://www.myrunningman.com/assets/epimg/091.jpg

Other

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

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of myrunningman.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.
`<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"]`
Myrunningman.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
24
17
17
19
48
11
16
28
16
any

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that myrunningman.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.
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.
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
Bootstrap
3.3.7
jQuery
1.12.4
jQuery UI
1.12.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.
URL Map URL
https://www.myrunningman.com/assets/js/jquery.qtip.min.js
https://www.myrunningman.com/assets/js/jquery.qtip.min.map
https://www.myrunningman.com/assets/js/jquery.min.js
https://www.myrunningman.com/assets/js/js.cookie.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://myrunningman.com/
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Includes front-end JavaScript libraries with known security vulnerabilities — 9 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
5
Medium
4
Medium

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
https://www.myrunningman.com/assets/epimg/574_temp.jpg
300 x 168
300 x 168
600 x 336
https://www.myrunningman.com/assets/epimg/575_temp.jpg
300 x 168
300 x 168
600 x 336
77

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for myrunningman.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 myrunningman.com on mobile screens.

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.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

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

Content Best Practices

Mobile Friendly

Document doesn't use legible font sizes — 54.02% 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
.label
13.51%
10.5px
.small, small
0.36%
11.9px
32.11%
< 12px
54.02%
≥ 12px
Tap targets are not sized appropriately — 26% 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
12x17
12x17
12x17
3
6x12
6
6x12
7
6x12
12x17
12x17
12x17
12x17
12x17
7
6x12
24
12x12
17
12x12
17
12x12
19
12x12
48
12x12
11
12x12
16
12x12
28
12x12
16
12x12
40x17
40x17
3
6x12
6
6x12
38x17
46x17
46x17
45x17
45x17
47x17
47x17
53x17
81x17
67x17
64x17
62x17
74x17
80x17
102x17
88x17
91x17
64x17
66x17
74x17
80x17
102x17
88x17
90x17
91x17
74x17
80x17
102x17
88x17
90x17
63x17
113x17
91x17
89x17
91x17
56x17
51x17
51x17
66x17
80x17
80x17
62x17
51x17
51x17
66x17
53x17
78x17
57x17
77x17
65x17
72x17
71x17
73x17
73x17
78x17
77x17
94x17
77x17
77x17
67x17
60x17
60x17
99x17
96x17
96x17
75x17
93x17
94x17
94x17
132x17
112x17
119x17
133x17
71x17
126x17
113x17
115x17
142x17
64x17
68x17
61x17
71x17
79x17
66x17
53x17
66x17
77x17
67x17
49x17
71x17
84x17
92x17
85x17
88x17
77x17
68x17
68x17
67x17
86x17
68x17
62x17
71x17
46x17
64x17
45x17
38x17
53x17
73x17
47x17
58x17
17
12x12
17
12x12
19
12x12
16
12x12
62x17
44x17
44x17
79x17
75x17
55x17
132x17
50x17
79x17
44x17
63x17
44x17
79x17
63x17
44x17
68x17
64x17
44x17
71x17
72x17
123x17
49x17
3
6x12
6
6x12
66x17
74x17
59x17
80x17
79x17
66x17
45x17
50x17
71x17
45x17
71x17
66x17
111x17
7
6x12
43x17
62x17

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

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

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of myrunningman.com 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: 104.21.25.146
Continent:
Country:
Region:
City:
Longitude:
Latitude:
Currencies:
Languages:

Web Hosting Provider

Name IP Address
Cloudflare, Inc.
Registration

Domain Registrant

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

Domain Registrar

Name IP Address
Cloudflare, Inc. 104.16.124.96
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: myrunningman.com
Issued By: E1
Valid From: 9th May, 2023
Valid To: 7th August, 2023
Subject: CN = myrunningman.com
Hash: 30208f6f
Issuer: CN = E1
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x04E399166CA6954EB53395EF3B0AD0EDDA81
Serial Number (Hex): 04E399166CA6954EB53395EF3B0AD0EDDA81
Valid From: 9th May, 2024
Valid To: 7th August, 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 : B7:3E:FB:24:DF:9C:4D:BA:75:F2:39:C5:BA:58:F4:6C:
5D:FC:42:CF:7A:9F:35:C4:9E:1D:09:81:25:ED:B4:99
Timestamp : May 10 00:56:57.946 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:16:7D:5B:F7:55:A9:B9:BF:EB:1A:38:E4:
A1:16:AB:DD:57:94:42:DF:E3:3A:69:4C:58:A0:50:BE:
BD:0E:9C:A9:02:21:00:99:B0:8D:E5:2C:1B:F3:E9:09:
BC:EF:A8:DD:01:CD:D7:44:77:8E:95:C6:ED:F3:FA:DE:
C4:BC:E5:D9:8E:9B:C0
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 7A:32:8C:54:D8:B7:2D:B6:20:EA:38:E0:52:1E:E9:84:
16:70:32:13:85:4D:3B:D2:2B:C1:3A:57:A3:52:EB:52
Timestamp : May 10 00:56:58.436 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:2D:00:76:40:FD:57:02:FF:A0:CE:F6:D2:
5C:73:82:C6:FF:EC:A2:57:DD:9E:9D:F1:99:16:9B:E2:
87:35:23:1D:02:21:00:89:81:C2:CF:9A:CA:1D:0B:FA:
3E:A0:96:2D:F5:04:40:21:87:F1:49:74:F1:55:2F:46:
84:EB:F2:C4:04:49:0B
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:myrunningman.com
DNS:*.myrunningman.com
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 15th May, 2023
Content-Type: text/html; charset=UTF-8
Expires: 19th November, 1981
Cache-Control: no-store, no-cache, must-revalidate
Server: cloudflare
Connection: keep-alive
Set-Cookie: *
Pragma: no-cache
X-Cache: HIT
CF-Cache-Status: DYNAMIC
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=0%2FyBR9jhHSLEK5xlk98SYtXtOXz5VnHAnSkB%2BiDMRnmh23GrlIYOjmDCimWD2zTMHQ2HRwZbZjqk2Ie5cdKO2jAOAs9IVOQS%2BuJ9jSbDzVodYTo9BnUKemuJk%2B1G7UZOHgTyali9lg%3D%3D"}],"group":"cf-nel","max_age":604800}
NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
CF-RAY: 7c79adffffc7c323-EWR
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400

Whois Lookup

Created: 12th September, 2016
Changed: 20th August, 2022
Expires: 12th September, 2023
Registrar: Cloudflare, Inc.
Status:
Nameservers: ben.ns.cloudflare.com
rose.ns.cloudflare.com
Owner Name: DATA REDACTED
Owner Organization: DATA REDACTED
Owner Street: DATA REDACTED
Owner Post Code: DATA REDACTED
Owner City: DATA REDACTED
Owner State: Ontario
Owner Country: CA
Owner Phone: DATA REDACTED
Owner Email: https://domaincontact.cloudflareregistrar.com/myrunningman.com
Admin Name: DATA REDACTED
Admin Organization: DATA REDACTED
Admin Street: DATA REDACTED
Admin Post Code: DATA REDACTED
Admin City: DATA REDACTED
Admin State: DATA REDACTED
Admin Country: DATA REDACTED
Admin Phone: DATA REDACTED
Admin Email: https://domaincontact.cloudflareregistrar.com/myrunningman.com
Tech Name: DATA REDACTED
Tech Organization: DATA REDACTED
Tech Street: DATA REDACTED
Tech Post Code: DATA REDACTED
Tech City: DATA REDACTED
Tech State: DATA REDACTED
Tech Country: DATA REDACTED
Tech Phone: DATA REDACTED
Tech Email: https://domaincontact.cloudflareregistrar.com/myrunningman.com
Billing Name: DATA REDACTED
Billing Organization: DATA REDACTED
Billing Street: DATA REDACTED
Billing Post Code: DATA REDACTED
Billing City: DATA REDACTED
Billing State: DATA REDACTED
Billing Country: DATA REDACTED
Billing Phone: DATA REDACTED
Billing Fax: DATA REDACTED
Billing Email: https://domaincontact.cloudflareregistrar.com/myrunningman.com
Full Whois: Domain Name: MYRUNNINGMAN.COM
Registry Domain ID: 2058882418_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.cloudflare.com
Registrar URL: https://www.cloudflare.com
Updated Date: 2022-08-20T09:01:09Z
Creation Date: 2016-09-12T14:29:03Z
Registrar Registration Expiration Date: 2023-09-12T14:29:03Z
Registrar: Cloudflare, Inc.
Registrar IANA ID: 1910
Domain Status: clienttransferprohibited https://icann.org/epp#clienttransferprohibited
Registry Registrant ID:
Registrant Name: DATA REDACTED
Registrant Organization: DATA REDACTED
Registrant Street: DATA REDACTED
Registrant City: DATA REDACTED
Registrant State/Province: Ontario
Registrant Postal Code: DATA REDACTED
Registrant Country: CA
Registrant Phone: DATA REDACTED
Registrant Phone Ext: DATA REDACTED
Registrant Fax: DATA REDACTED
Registrant Fax Ext: DATA REDACTED
Registrant Email: https://domaincontact.cloudflareregistrar.com/myrunningman.com
Registry Admin ID:
Admin Name: DATA REDACTED
Admin Organization: DATA REDACTED
Admin Street: DATA REDACTED
Admin City: DATA REDACTED
Admin State/Province: DATA REDACTED
Admin Postal Code: DATA REDACTED
Admin Country: DATA REDACTED
Admin Phone: DATA REDACTED
Admin Phone Ext: DATA REDACTED
Admin Fax: DATA REDACTED
Admin Fax Ext: DATA REDACTED
Admin Email: https://domaincontact.cloudflareregistrar.com/myrunningman.com
Registry Tech ID:
Tech Name: DATA REDACTED
Tech Organization: DATA REDACTED
Tech Street: DATA REDACTED
Tech City: DATA REDACTED
Tech State/Province: DATA REDACTED
Tech Postal Code: DATA REDACTED
Tech Country: DATA REDACTED
Tech Phone: DATA REDACTED
Tech Phone Ext: DATA REDACTED
Tech Fax: DATA REDACTED
Tech Fax Ext: DATA REDACTED
Tech Email: https://domaincontact.cloudflareregistrar.com/myrunningman.com
Registry Billing ID:
Billing Name: DATA REDACTED
Billing Organization: DATA REDACTED
Billing Street: DATA REDACTED
Billing City: DATA REDACTED
Billing State/Province: DATA REDACTED
Billing Postal Code: DATA REDACTED
Billing Country: DATA REDACTED
Billing Phone: DATA REDACTED
Billing Phone Ext: DATA REDACTED
Billing Fax: DATA REDACTED
Billing Fax Ext: DATA REDACTED
Billing Email: https://domaincontact.cloudflareregistrar.com/myrunningman.com
Name Server: ben.ns.cloudflare.com
Name Server: rose.ns.cloudflare.com
DNSSEC: signedDelegation
Registrar Abuse Contact Email: registrar-abuse@cloudflare.com
Registrar Abuse Contact Phone: +1.4153197517
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2023-05-15T07:31:09Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

Cloudflare provides more than 13 million domains with the tools to give their global users a faster, more secure, and more reliable internet experience.

NOTICE:

Data in the Cloudflare Registrar WHOIS database is provided to you by Cloudflare
under the terms and conditions at https://www.cloudflare.com/domain-registration-agreement/

By submitting this query, you agree to abide by these terms.

Register your domain name at https://www.cloudflare.com/registrar/

Nameservers

Name IP Address
ben.ns.cloudflare.com 172.64.33.103
rose.ns.cloudflare.com 172.64.32.141
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address