Overview Review Traffic Revenue SEO
Hosting Registration Security Technical Related

running.com

running.com may not be SSL secured

Free website and domain report on running.com

Last Updated: 30th April, 2020 Update Now
Overview

Snoop Summary for running.com

This is a free and comprehensive report about running.com. The domain running.com is currently hosted on a server located in Ashburn, Virginia in United States with the IP address 23.23.86.44, where USD is the local currency and the local language is English. Running.com has the potential to be earning an estimated $1 USD per day from advertising revenue. If running.com was to be sold it would possibly be worth $776 USD (based on the daily revenue potential of the website over a 24 month period). Running.com receives an estimated 368 unique visitors every day - a decent amount of traffic! This report was last updated 30th April, 2020.

About running.com

Site Preview: running.com running.com
Title: Running.com
Description:
Keywords and Tags: amazon associates program, opportunities, parked domain, partners programs
Related Terms:
Fav Icon:
Age: Over 25 years old
Domain Created: 22nd May, 1998
Domain Updated: 25th January, 2018
Domain Expires: 21st May, 2027
Review

Snoop Score

1/5

Valuation

$776 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 3,422,167
Alexa Reach: <0.0001%
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 368
Monthly Visitors: 11,201
Yearly Visitors: 134,320
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $32 USD
Yearly Revenue: $383 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: running.com 11
Domain Name: running 7
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 1.52 seconds
Load Time Comparison: Faster than 55% of sites

PageSpeed Insights

Avg. (All Categories) 73
Performance 99
Accessibility 85
Best Practices 69
SEO 80
Progressive Web App 31
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
99

Performance

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

Metrics

First Contentful Paint — 0.6 s
The time taken for the first image or text on the page to be rendered.
First Meaningful Paint — 0.9 s
The time taken for the primary content of the page to be rendered.
Speed Index — 0.8 s
The time taken for the page contents to be visibly populated.
Time to Interactive — 1.5 s
The time taken for the page to become fully interactive.
First CPU Idle — 1.3 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 110 ms
Users could experience a delay when interacting with the page.

Other

Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive running.com as laggy when the latency is higher than 0.05 seconds.
Total Blocking Time — 150 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).
Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://running.com/
0
68.987000267953
255
0
301
text/html
http://www.running.com/
69.55000013113
140.65399998799
4503
7168
200
text/html
Document
http://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js
153.76899996772
161.88800008968
30890
86927
200
text/javascript
Script
http://www.running.com/assets/application-ea87d7f1cf81efea754ac69b6a6922a8.js
154.04700022191
194.75600030273
113907
314521
200
application/x-javascript
Script
http://www.running.com/media/W1siZiIsIjIwMTIvMDQvMjYvMjAvMDcvNDQvNTc4L2F0aGxldGljc2hvZXMuY29tLmpwZyJdLFsicCIsInRodW1iIiwiMjUweDIwMCMiXV0/athleticshoes.com.jpg
154.29600002244
173.60900016502
12539
12147
200
image/jpeg
Image
http://www.running.com/assets/abp2-4831d5b24977f8140fd9aa25543527f2.js
192.32700020075
213.86600006372
797
1296
200
application/x-javascript
Script
http://www.running.com/assets/ads-832e97bfd2d3e735f6dc8a30dd7190bc.js
192.59200012311
214.6490002051
441
115
200
application/x-javascript
Script
http://www.google.com/adsense/domains/caf.js
192.79100000858
217.949999962
58927
166054
200
text/javascript
Script
https://www.googletagmanager.com/gtag/js?id=UA-32054758-1
193.09800025076
216.95400029421
30892
81636
200
application/javascript
Script
http://privacy.digimedia.com/check_cookie_country_code.js
192.96000013128
233.89800032601
5249
4775
200
application/javascript
Script
http://www.running.com/assets/style-85cdb3be1709c9028b204b38f8ccb358.css
193.2200002484
233.40400028974
362
53
200
text/css
Stylesheet
http://www.running.com/assets/google_caf_reflex-2b4f1e055ab27b739ad375f09d99be17.css
194.06899996102
216.09300002456
997
1761
200
text/css
Stylesheet
https://www.google.com/afs/ads/i/iframe.html
294.81700016186
301.48900020868
846
0
200
text/html
Document
https://www.google.com/afs/ads/i/iframe.html
301.15299997851
305.95800001174
834
0
200
text/html
Document
https://www.google.com/dp/ads?adrep=3&r=m&client=dp-digimedia3_js&channel=digi-caf_pef%2Cdigimedia-template-04&adtest=false&psid=9039920606&kw=running&terms=running%2Crunning%20shoes%2Crunning%20apparel%2Crunning%20shorts%2Crunning%20magazine%2Cjogging%2Crunning%20equipment%2Cfitness%20training&swp=as-drid-oo-1626960400946279&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300003%2C17300162%2C17300165%2C17300167&format=s%7Cs%7Cr8&num=0&output=afd_ads&domain_name=www.running.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1588250656721&u_w=800&u_h=600&biw=1350&bih=940&psw=1334&psh=390&frm=0&uio=sl1sr1---st18&cont=gencats&csize=w478h0&inames=slave-2-1&jsv=23388&rurl=http%3A%2F%2Fwww.running.com%2F
308.29100031406
334.32900020853
0
0
-1
Document
http://www.running.com/px.gif?ch=1&rn=4.538794573238042
311.4990000613
348.19799987599
776
43
200
image/gif
Image
http://www.running.com/px.gif?ch=2&rn=4.538794573238042
311.84499990195
347.87200018764
776
43
200
image/gif
Image
https://www.google.com/dp/ads?adrep=3&r=m&client=dp-digimedia3_js&channel=digi-caf_pef%2Cdigimedia-template-04&adtest=false&psid=9039920606&kw=running&terms=running%2Crunning%20shoes%2Crunning%20apparel%2Crunning%20shorts%2Crunning%20magazine%2Cjogging%2Crunning%20equipment%2Cfitness%20training&swp=as-drid-oo-1626960400946279&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300003%2C17300162%2C17300165%2C17300167&format=s%7Cs%7Cr8&num=0&output=afd_ads&domain_name=www.running.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1588250656721&u_w=800&u_h=600&biw=1350&bih=940&psw=1334&psh=390&frm=0&uio=sl1sr1---st18&cont=gencats&csize=w478h0&inames=slave-2-1&jsv=23388&rurl=http%3A%2F%2Fwww.running.com%2F
343.24200032279
435.41300017387
7638
10214
200
text/html
Document
https://www.google.com/afs/ads/i/iframe.html
346.40000015497
354.97800027952
1510
1243
200
text/html
Document
https://www.google.com/afs/ads/i/iframe.html
348.62000029534
357.10899997503
1502
1243
200
text/html
Document
https://www.google-analytics.com/analytics.js
386.93000003695
403.17999990657
18794
45229
200
text/javascript
Script
https://www.google-analytics.com/r/collect?v=1&_v=j81&a=1675585906&t=pageview&_s=1&dl=http%3A%2F%2Fwww.running.com%2F&dp=%2F&ul=en-us&de=UTF-8&dt=running.com&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAUAB~&jid=906913574&gjid=182828222&cid=483285344.1588250657&tid=UA-32054758-1&_gid=1180969364.1588250657&_r=1&gtm=2ou4f0&z=1039963906
439.38599992543
444.41700028256
580
35
200
image/gif
Image
https://www.google-analytics.com/collect?v=1&_v=j81&a=1675585906&t=event&_s=2&dl=http%3A%2F%2Fwww.running.com%2F&dp=%2F&ul=en-us&de=UTF-8&dt=running.com&sd=24-bit&sr=800x600&vp=1350x940&je=0&ec=domain_name&ea=index&el=running.com&_u=IEBAAUAB~&jid=&gjid=&cid=483285344.1588250657&tid=UA-32054758-1&_gid=1180969364.1588250657&gtm=2ou4f0&z=2143993120
440.23799989372
443.91599996015
594
35
200
image/gif
Image
https://www.google.com/adsense/domains/caf.js
450.80000022426
468.8160000369
60725
166088
200
text/javascript
Script
https://www.google.com/js/bg/Qh1z7zbz5tCe3803wA8GK4W8DMNijuMntDnjdovpGbs.js
584.89400008693
589.31299997494
6046
12350
200
text/javascript
Script
https://www.google.com/js/bg/Qh1z7zbz5tCe3803wA8GK4W8DMNijuMntDnjdovpGbs.js
585.76299995184
590.24900011718
6046
12350
200
text/javascript
Script
https://www.google.com/js/bg/Qh1z7zbz5tCe3803wA8GK4W8DMNijuMntDnjdovpGbs.js
592.10500027984
596.23400028795
6046
12350
200
text/javascript
Script
http://www.running.com/px.gif?type=not_blocked&n=6.368310120301544
920.78000027686
947.106000036
776
43
200
image/gif
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
174.568
8.326
200.411
25.179
226.804
7.523
249.998
27.319
280.784
8.519
295.051
84.949
385.091
6.345
393.736
6.602
400.358
6.281
406.943
13.342
439.818
31.545
471.75
6.542
517.197
77.048
598.313
11.054
626.69
102.712
729.466
100.693
833.313
111.379
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Running.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Running.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Running.com should consider minifying CSS files.
Minify JavaScript — Potential savings of 54 KB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Running.com should consider minifying JS files.
URL Size (Bytes) Potential Savings (Bytes)
http://www.running.com/assets/application-ea87d7f1cf81efea754ac69b6a6922a8.js
113907
55219
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Running.com 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.
Serve images in next-gen formats
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
Enable text compression — Potential savings of 3 KB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Size (Bytes) Potential Savings (Bytes)
http://privacy.digimedia.com/check_cookie_country_code.js
4775
3096
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Server response times are low (TTFB) — Root document took 70 ms
Time to First Byte (TTFB) identifies the time at which the server sends a response.
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Running.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
(Start) http://running.com/
0
http://www.running.com/
190
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Running.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.

Diagnostics

Avoids enormous network payloads — Total size was 363 KB
Large network payloads can cost users money and are linked to long load times.
URL Size (Bytes)
http://www.running.com/assets/application-ea87d7f1cf81efea754ac69b6a6922a8.js
113907
https://www.google.com/adsense/domains/caf.js
60725
http://www.google.com/adsense/domains/caf.js
58927
https://www.googletagmanager.com/gtag/js?id=UA-32054758-1
30892
http://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js
30890
https://www.google-analytics.com/analytics.js
18794
http://www.running.com/media/W1siZiIsIjIwMTIvMDQvMjYvMjAvMDcvNDQvNTc4L2F0aGxldGljc2hvZXMuY29tLmpwZyJdLFsicCIsInRodW1iIiwiMjUweDIwMCMiXV0/athleticshoes.com.jpg
12539
https://www.google.com/dp/ads?adrep=3&r=m&client=dp-digimedia3_js&channel=digi-caf_pef%2Cdigimedia-template-04&adtest=false&psid=9039920606&kw=running&terms=running%2Crunning%20shoes%2Crunning%20apparel%2Crunning%20shorts%2Crunning%20magazine%2Cjogging%2Crunning%20equipment%2Cfitness%20training&swp=as-drid-oo-1626960400946279&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300003%2C17300162%2C17300165%2C17300167&format=s%7Cs%7Cr8&num=0&output=afd_ads&domain_name=www.running.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1588250656721&u_w=800&u_h=600&biw=1350&bih=940&psw=1334&psh=390&frm=0&uio=sl1sr1---st18&cont=gencats&csize=w478h0&inames=slave-2-1&jsv=23388&rurl=http%3A%2F%2Fwww.running.com%2F
7638
https://www.google.com/js/bg/Qh1z7zbz5tCe3803wA8GK4W8DMNijuMntDnjdovpGbs.js
6046
https://www.google.com/js/bg/Qh1z7zbz5tCe3803wA8GK4W8DMNijuMntDnjdovpGbs.js
6046
Uses efficient cache policy on static assets — 1 resource found
Running.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) Size (Bytes)
https://www.google-analytics.com/analytics.js
7200000
18794
Avoids an excessive DOM size — 54 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
54
Maximum DOM Depth
SHOW DETAILS
10
Maximum Child Elements
SHOW DETAILS
16
Avoid chaining critical requests — 5 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Running.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.4 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.google.com/adsense/domains/caf.js
393.699
351.076
10.102
Other
121.183
11.379
3.621
http://www.running.com/assets/application-ea87d7f1cf81efea754ac69b6a6922a8.js
58.99
48.211
6.623
Minimizes main-thread work — 0.7 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
532.341
Other
69.278
Script Parsing & Compilation
38.436
Style & Layout
33.11
Garbage Collection
19.478
Parse HTML & CSS
14.731
Rendering
10.936
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 — 28 requests • 365 KB
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
28
373248
Script
12
338760
Document
7
16833
Image
6
16041
Stylesheet
2
1359
Other
1
255
Media
0
0
Font
0
0
Third-party
17
237119
Minimize third-party usage — Third-party code blocked the main thread for 120 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 Size (Bytes) Main-Thread Blocking Time (Ms)
SHOW DETAILS
150120
124.446
SHOW DETAILS
30892
0
SHOW DETAILS
30890
0
SHOW DETAILS
19968
0

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.

Opportunities

Eliminate render-blocking resources — Potential savings of 260 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Running.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Size (Bytes) Potential Savings (Ms)
http://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js
30890
230
85

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of running.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.
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.
`[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-*]` 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.

Audio and video

`<audio>` elements contain a `<track>` element with `[kind="captions"]`
Running.com may provide assistance to deaf or hearing-impaired users with captions on audio elements.
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Running.com may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Running.com may provide relevant information that dialogue cannot, by using audio descriptions.

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.
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 `[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.

Contrast

Background and foreground colors have a sufficient contrast ratio
Many (if not most) users find low-contrast text difficult or impossible to read.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>` or `<template>` 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.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
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.

Best practices

`[id]` attributes on the page are unique
It is advised to keep all id attributes unique in order to prevent instances from being overlooked by screen readers and other assistive technologies.
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.

Internationalization and localization

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

Names and labels

`<frame>` or `<iframe>` elements do not have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Failing Elements
iframe
iframe
iframe

Internationalization and localization

`<html>` element does not have 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.
Failing Elements
html

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.
Headings don't skip levels
Ensure that headings create an outline for the page and that heading levels are not skipped.
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.
69

Best Practices

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

Other

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
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.
Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.12.4
jQuery (Fast path)
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
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.
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.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.

Other

Does not use HTTPS — 14 insecure requests 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
http://running.com/
http://www.running.com/
http://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js
http://www.running.com/assets/application-ea87d7f1cf81efea754ac69b6a6922a8.js
http://www.running.com/media/W1siZiIsIjIwMTIvMDQvMjYvMjAvMDcvNDQvNTc4L2F0aGxldGljc2hvZXMuY29tLmpwZyJdLFsicCIsInRodW1iIiwiMjUweDIwMCMiXV0/athleticshoes.com.jpg
http://www.running.com/assets/abp2-4831d5b24977f8140fd9aa25543527f2.js
http://www.running.com/assets/ads-832e97bfd2d3e735f6dc8a30dd7190bc.js
http://www.google.com/adsense/domains/caf.js
http://privacy.digimedia.com/check_cookie_country_code.js
http://www.running.com/assets/style-85cdb3be1709c9028b204b38f8ccb358.css
http://www.running.com/assets/google_caf_reflex-2b4f1e055ab27b739ad375f09d99be17.css
http://www.running.com/px.gif?ch=1&rn=4.538794573238042
http://www.running.com/px.gif?ch=2&rn=4.538794573238042
http://www.running.com/px.gif?type=not_blocked&n=6.368310120301544
Uses `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.
URL Location
https://www.google.com/adsense/domains/caf.js
line: 206
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 — 2 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
SHOW DETAILS
2
Medium
80

SEO

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

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
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

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.

Mobile Friendly

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of running.com on mobile screens.

Content Best Practices

Document does not have a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.

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

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

Fast and reliable

Page load is fast enough on mobile networks
Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.

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.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.

Fast and reliable

Current page does not respond with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` does not respond with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

Does not use HTTPS — 14 insecure requests 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
http://running.com/
http://www.running.com/
http://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js
http://www.running.com/assets/application-ea87d7f1cf81efea754ac69b6a6922a8.js
http://www.running.com/media/W1siZiIsIjIwMTIvMDQvMjYvMjAvMDcvNDQvNTc4L2F0aGxldGljc2hvZXMuY29tLmpwZyJdLFsicCIsInRodW1iIiwiMjUweDIwMCMiXV0/athleticshoes.com.jpg
http://www.running.com/assets/abp2-4831d5b24977f8140fd9aa25543527f2.js
http://www.running.com/assets/ads-832e97bfd2d3e735f6dc8a30dd7190bc.js
http://www.google.com/adsense/domains/caf.js
http://privacy.digimedia.com/check_cookie_country_code.js
http://www.running.com/assets/style-85cdb3be1709c9028b204b38f8ccb358.css
http://www.running.com/assets/google_caf_reflex-2b4f1e055ab27b739ad375f09d99be17.css
http://www.running.com/px.gif?ch=1&rn=4.538794573238042
http://www.running.com/px.gif?ch=2&rn=4.538794573238042
http://www.running.com/px.gif?type=not_blocked&n=6.368310120301544
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.
Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

Does not redirect HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
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 have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of running.com on mobile screens.
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.

Manual Checks

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

1.63 seconds
First Contentful Paint (FCP)
51%
39%
10%

0.04 seconds
First Input Delay (FID)
96%
2%
2%

Simulate loading on mobile
75

Performance

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

Opportunities

Properly size images
Images can slow down the page's load time. Running.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Running.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Running.com should consider minifying CSS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Running.com 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.
Serve images in next-gen formats
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
Enable text compression — Potential savings of 3 KB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Size (Bytes) Potential Savings (Bytes)
http://privacy.digimedia.com/check_cookie_country_code.js
4775
3096
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Server response times are low (TTFB) — Root document took 90 ms
Time to First Byte (TTFB) identifies the time at which the server sends a response.
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Running.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
(Start) http://running.com/
0
http://www.running.com/
630
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Running.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.

Diagnostics

Avoids enormous network payloads — Total size was 351 KB
Large network payloads can cost users money and are linked to long load times.
URL Size (Bytes)
http://www.running.com/assets/application-ea87d7f1cf81efea754ac69b6a6922a8.js
113906
https://www.google.com/adsense/domains/caf.js
60555
http://www.google.com/adsense/domains/caf.js
58943
https://www.googletagmanager.com/gtag/js?id=UA-32054758-1
30892
http://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js
30890
https://www.google-analytics.com/analytics.js
18794
https://www.google.com/dp/ads?adrep=3&r=m&cpp=0&client=dp-digimedia3_js&channel=afsonly%2Cdigimedia-template-12&adtest=false&psid=9039920606&kw=running&terms=running%2Crunning%20shoes%2Crunning%20apparel%2Crunning%20shorts%2Crunning%20magazine%2Cjogging%2Crunning%20equipment%2Cfitness%20training&swp=as-drid-oo-1626960400946279&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300003%2C17300162%2C17300169%2C17300171&format=s%7Cs%7Cr8&num=0&output=afd_ads&domain_name=www.running.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1588250666802&u_w=412&u_h=660&biw=412&bih=660&psw=396&psh=104&frm=0&uio=sl1sr1---st18&cont=gencats&csize=w396h0&inames=slave-2-1&jsv=23388&rurl=http%3A%2F%2Fwww.running.com%2F
7621
https://www.google.com/js/bg/Qh1z7zbz5tCe3803wA8GK4W8DMNijuMntDnjdovpGbs.js
6046
https://www.google.com/js/bg/Qh1z7zbz5tCe3803wA8GK4W8DMNijuMntDnjdovpGbs.js
6046
https://www.google.com/js/bg/Qh1z7zbz5tCe3803wA8GK4W8DMNijuMntDnjdovpGbs.js
6046
Uses efficient cache policy on static assets — 1 resource found
Running.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) Size (Bytes)
https://www.google-analytics.com/analytics.js
7200000
18794
Avoids an excessive DOM size — 50 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
50
Maximum DOM Depth
SHOW DETAILS
10
Maximum Child Elements
SHOW DETAILS
16
Avoid chaining critical requests — 5 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Running.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.
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 — 28 requests • 352 KB
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
28
360748
Script
12
338611
Document
7
16738
Image
6
4204
Stylesheet
2
936
Other
1
259
Media
0
0
Font
0
0
Third-party
18
237717

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.

Other

Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://running.com/
0
25.637999991886
259
0
301
text/html
http://www.running.com/
26.254000025801
117.71100002807
4364
6913
200
text/html
Document
http://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js
151.39399998588
157.73000003537
30890
86927
200
text/javascript
Script
http://www.running.com/assets/application-ea87d7f1cf81efea754ac69b6a6922a8.js
151.60899999319
203.31399998395
113906
314521
200
application/x-javascript
Script
http://www.running.com/assets/abp2-4831d5b24977f8140fd9aa25543527f2.js
151.79000003263
182.23899998702
797
1296
200
application/x-javascript
Script
http://www.running.com/assets/ads-832e97bfd2d3e735f6dc8a30dd7190bc.js
152.25700003793
183.66300000343
441
115
200
application/x-javascript
Script
http://www.google.com/adsense/domains/caf.js
152.39000000292
182.87600000622
58943
166079
200
text/javascript
Script
https://www.googletagmanager.com/gtag/js?id=UA-32054758-1
152.50500000548
181.59400002332
30892
81636
200
application/javascript
Script
http://privacy.digimedia.com/check_cookie_country_code.js
152.66700001666
183.40899999021
5255
4775
200
application/javascript
Script
http://www.running.com/assets/style-85cdb3be1709c9028b204b38f8ccb358.css
214.77600000799
245.01399998553
362
53
200
text/css
Stylesheet
http://www.running.com/assets/mobile-7b7fa1a9a2489ff075167a8fa764dd14.css
214.91800004151
234.44999998901
574
263
200
text/css
Stylesheet
http://www.running.com/px.gif?ch=1&rn=2.2404093042884856
315.48400002066
349.2350000306
776
43
200
image/gif
Image
http://www.running.com/px.gif?ch=2&rn=2.2404093042884856
315.73400000343
369.04499999946
776
43
200
image/gif
Image
https://www.google.com/afs/ads/i/iframe.html
368.94800001755
388.87000002433
834
0
200
text/html
Document
https://www.google.com/afs/ads/i/iframe.html
388.73900001636
414.02100003324
846
0
200
text/html
Document
https://www.google.com/dp/ads?adrep=3&r=m&cpp=0&client=dp-digimedia3_js&channel=afsonly%2Cdigimedia-template-12&adtest=false&psid=9039920606&kw=running&terms=running%2Crunning%20shoes%2Crunning%20apparel%2Crunning%20shorts%2Crunning%20magazine%2Cjogging%2Crunning%20equipment%2Cfitness%20training&swp=as-drid-oo-1626960400946279&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300003%2C17300162%2C17300169%2C17300171&format=s%7Cs%7Cr8&num=0&output=afd_ads&domain_name=www.running.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1588250666802&u_w=412&u_h=660&biw=412&bih=660&psw=396&psh=104&frm=0&uio=sl1sr1---st18&cont=gencats&csize=w396h0&inames=slave-2-1&jsv=23388&rurl=http%3A%2F%2Fwww.running.com%2F
392.67500001006
446.34600001154
0
0
-1
Document
https://www.google.com/dp/ads?adrep=3&r=m&cpp=0&client=dp-digimedia3_js&channel=afsonly%2Cdigimedia-template-12&adtest=false&psid=9039920606&kw=running&terms=running%2Crunning%20shoes%2Crunning%20apparel%2Crunning%20shorts%2Crunning%20magazine%2Cjogging%2Crunning%20equipment%2Cfitness%20training&swp=as-drid-oo-1626960400946279&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300003%2C17300162%2C17300169%2C17300171&format=s%7Cs%7Cr8&num=0&output=afd_ads&domain_name=www.running.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1588250666802&u_w=412&u_h=660&biw=412&bih=660&psw=396&psh=104&frm=0&uio=sl1sr1---st18&cont=gencats&csize=w396h0&inames=slave-2-1&jsv=23388&rurl=http%3A%2F%2Fwww.running.com%2F
460.27899999171
553.05500002578
7621
10186
200
text/html
Document
https://www.google.com/afs/ads/i/iframe.html
470.4700000002
511.22400001623
1525
1243
200
text/html
Document
https://www.google.com/afs/ads/i/iframe.html
479.47200003546
500.44899998466
1548
1243
200
text/html
Document
https://www.google-analytics.com/analytics.js
590.92899999814
598.77400001278
18794
45229
200
text/javascript
Script
https://www.google.com/adsense/domains/caf.js
630.97300002119
647.26699999301
60555
166054
200
text/javascript
Script
https://www.google-analytics.com/r/collect?v=1&_v=j81&a=1970876936&t=pageview&_s=1&dl=http%3A%2F%2Fwww.running.com%2F&dp=%2F&ul=en-us&de=UTF-8&dt=running.com&sd=24-bit&sr=412x660&vp=412x660&je=0&_u=IEBAAUAB~&jid=894929760&gjid=101366156&cid=200781306.1588250667&tid=UA-32054758-1&_gid=2062311768.1588250667&_r=1&gtm=2ou4f0&z=529386820
656.69100004015
662.04999998445
580
35
200
image/gif
Image
https://www.google-analytics.com/collect?v=1&_v=j81&a=1970876936&t=event&_s=2&dl=http%3A%2F%2Fwww.running.com%2F&dp=%2F&ul=en-us&de=UTF-8&dt=running.com&sd=24-bit&sr=412x660&vp=412x660&je=0&ec=domain_name&ea=index&el=running.com&_u=IEBAAUAB~&jid=&gjid=&cid=200781306.1588250667&tid=UA-32054758-1&_gid=2062311768.1588250667&gtm=2ou4f0&z=541019213
657.02799998689
662.52300003543
594
35
200
image/gif
Image
https://www.gstatic.com/domainads/images/chevron-white.png
740.10200001067
745.66600000253
702
189
200
image/png
Image
https://www.google.com/js/bg/Qh1z7zbz5tCe3803wA8GK4W8DMNijuMntDnjdovpGbs.js
826.68200001353
840.92500002589
6046
12350
200
text/javascript
Script
https://www.google.com/js/bg/Qh1z7zbz5tCe3803wA8GK4W8DMNijuMntDnjdovpGbs.js
830.5929999915
840.49000003142
6046
12350
200
text/javascript
Script
http://www.running.com/px.gif?type=not_blocked&n=1.4697589809716785
840.37799999351
881.34800002445
776
43
200
image/gif
Image
https://www.google.com/js/bg/Qh1z7zbz5tCe3803wA8GK4W8DMNijuMntDnjdovpGbs.js
841.97200002382
848.15099998377
6046
12350
200
text/javascript
Script
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
207.359
14.75
242.235
49.994
296.134
38.227
338.227
140.227
487.596
8.17
495.836
8.251
504.831
55.805
560.673
41.846
605.676
44.307
649.999
17.614
669.025
5.863
674.905
6.484
681.411
5.235
686.66
9.973
708.147
25.173
751.558
84.172
837.481
5.305
845.918
31.808
877.753
16.963
894.789
5.097
903.974
9.689
918.888
108.872
1027.822
104.911
1140.049
88.326
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Metrics

First Contentful Paint — 2.8 s
The time taken for the first image or text on the page to be rendered.
First Meaningful Paint — 3.1 s
The time taken for the primary content of the page to be rendered.
Speed Index — 3.4 s
The time taken for the page contents to be visibly populated.
Time to Interactive — 6.0 s
The time taken for the page to become fully interactive.
First CPU Idle — 5.4 s
The time taken for the page's main thread to be quiet enough to handle input.

Opportunities

Eliminate render-blocking resources — Potential savings of 430 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Running.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Size (Bytes) Potential Savings (Ms)
http://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js
30890
930
Minify JavaScript — Potential savings of 54 KB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Running.com should consider minifying JS files.
URL Size (Bytes) Potential Savings (Bytes)
http://www.running.com/assets/application-ea87d7f1cf81efea754ac69b6a6922a8.js
113906
55218

Diagnostics

Reduce JavaScript execution time — 2.9 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.google.com/adsense/domains/caf.js
1639.812
1480.104
41.636
Other
926.404
54.5
16.996
http://www.running.com/
515.352
486.168
6.132
http://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js
413.664
371.368
8.876
http://www.running.com/assets/application-ea87d7f1cf81efea754ac69b6a6922a8.js
181.892
132.38
43.248
https://www.googletagmanager.com/gtag/js?id=UA-32054758-1
107.608
89.72
17.888
https://www.google-analytics.com/analytics.js
98.348
93.268
5.08
http://www.google.com/adsense/domains/caf.js
77.996
49.228
20.056
Minimize main-thread work — 4.0 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
2786.324
Other
437.856
Style & Layout
323.904
Script Parsing & Compilation
176
Rendering
147.692
Parse HTML & CSS
87.656
Garbage Collection
47.32

Other

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

Metrics

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

Other

Estimated Input Latency — 210 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive running.com as laggy when the latency is higher than 0.05 seconds.
Total Blocking Time — 1,680 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).

Diagnostics

Reduce the impact of third-party code — Third-party code blocked the main thread for 1,390 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 Size (Bytes) Main-Thread Blocking Time (Ms)
SHOW DETAILS
150010
1068.092
SHOW DETAILS
31592
264.924
SHOW DETAILS
19968
38.852
SHOW DETAILS
30892
18.52
85

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of running.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.
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.
`[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-*]` 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.

Audio and video

`<audio>` elements contain a `<track>` element with `[kind="captions"]`
Running.com may provide assistance to deaf or hearing-impaired users with captions on audio elements.
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Running.com may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Running.com may provide relevant information that dialogue cannot, by using audio descriptions.

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.
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 `[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.

Contrast

Background and foreground colors have a sufficient contrast ratio
Many (if not most) users find low-contrast text difficult or impossible to read.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>` or `<template>` 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.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
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.

Best practices

`[id]` attributes on the page are unique
It is advised to keep all id attributes unique in order to prevent instances from being overlooked by screen readers and other assistive technologies.
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.

Internationalization and localization

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

Names and labels

`<frame>` or `<iframe>` elements do not have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Failing Elements
iframe
iframe
iframe

Internationalization and localization

`<html>` element does not have 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.
Failing Elements
html

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.
Headings don't skip levels
Ensure that headings create an outline for the page and that heading levels are not skipped.
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.
69

Best Practices

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

Other

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
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.
Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.12.4
jQuery (Fast path)
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
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.
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.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.

Other

Does not use HTTPS — 13 insecure requests 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
http://running.com/
http://www.running.com/
http://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js
http://www.running.com/assets/application-ea87d7f1cf81efea754ac69b6a6922a8.js
http://www.running.com/assets/abp2-4831d5b24977f8140fd9aa25543527f2.js
http://www.running.com/assets/ads-832e97bfd2d3e735f6dc8a30dd7190bc.js
http://www.google.com/adsense/domains/caf.js
http://privacy.digimedia.com/check_cookie_country_code.js
http://www.running.com/assets/style-85cdb3be1709c9028b204b38f8ccb358.css
http://www.running.com/assets/mobile-7b7fa1a9a2489ff075167a8fa764dd14.css
http://www.running.com/px.gif?ch=1&rn=2.2404093042884856
http://www.running.com/px.gif?ch=2&rn=2.2404093042884856
http://www.running.com/px.gif?type=not_blocked&n=1.4697589809716785
Uses `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.
URL Location
https://www.google.com/adsense/domains/caf.js
line: 206
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 — 2 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
SHOW DETAILS
2
Medium
91

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for running.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 running.com on mobile screens.
Document uses legible font sizes — 100% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
Legible text
100.00%
≥ 12px
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
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.

Content Best Practices

Document does not have a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.

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

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

Fast and reliable

Page load is fast enough on mobile networks
Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.

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 running.com on mobile screens.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.

Fast and reliable

Current page does not respond with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` does not respond with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

Does not use HTTPS — 13 insecure requests 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
http://running.com/
http://www.running.com/
http://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js
http://www.running.com/assets/application-ea87d7f1cf81efea754ac69b6a6922a8.js
http://www.running.com/assets/abp2-4831d5b24977f8140fd9aa25543527f2.js
http://www.running.com/assets/ads-832e97bfd2d3e735f6dc8a30dd7190bc.js
http://www.google.com/adsense/domains/caf.js
http://privacy.digimedia.com/check_cookie_country_code.js
http://www.running.com/assets/style-85cdb3be1709c9028b204b38f8ccb358.css
http://www.running.com/assets/mobile-7b7fa1a9a2489ff075167a8fa764dd14.css
http://www.running.com/px.gif?ch=1&rn=2.2404093042884856
http://www.running.com/px.gif?ch=2&rn=2.2404093042884856
http://www.running.com/px.gif?type=not_blocked&n=1.4697589809716785
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.
Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

Does not redirect HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
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.

Manual Checks

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

Server Location

Server IP Address: 23.23.86.44
Continent: North America
Country: United States
United States Flag
Region: Virginia
City: Ashburn
Longitude: -77.4728
Latitude: 39.0481
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Amazon Data Services NoVa
Registration

Domain Registrant

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

Domain Registrar

Name IP Address
NameCheap, Inc. 104.16.100.56
Security

Visitor Safety

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

SSL/TLS Certificate

Technical

DNS Lookup

A Records

Host IP Address Class TTL
running.com. 23.23.86.44 IN 599

NS Records

Host Nameserver Class TTL
running.com. ns2.digimedia.com. IN 599
running.com. ns1.digimedia.com. IN 599

MX Records

Priority Host Server Class TTL
1000 running.com. 0.0.0.0. IN 599

SOA Records

Domain Name Primary NS Responsible Email TTL
running.com. ns1.digimedia.com. dns.digimedia.com. 599

TXT Records

Host Value Class TTL
running.com. v=spf1 IN 599

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 30th April, 2020
Content-Type: text/html; charset=utf-8
Server: nginx/1.10.1
Cache-Control: max-age=0, private, must-revalidate
Connection: keep-alive
X-Adblock-Key: MFwwDQYJKoZIhvcNAQEBBQADSwAwSAJBAL/3/SrV7P8AsTHMFSpPmYbyv2PkACHwmG9Z+1IFZq3vA54IN7pQcGnhgNo+8SN9r/KtUWCb9OPqTfWM1N4w/EUCAwEAAQ==_rIDk+5KJOKVELrnT/sqIOV4wpmM4LT70XojTgK0ciNtem8sTVRp3+MFf/gIiAcyBy2WCvmJ54iOt1oUzWk76gg==
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: *
Access-Control-Request-Method: *
Access-Control-Allow-Headers: *
Access-Control-Max-Age: 86400
X-UA-Compatible: IE=Edge,chrome=1
ETag: "4bed20bba04d57bf6f739e60ee2a7b79"
Set-Cookie: *
X-Request-Id: f96b691b0b4f688ddf5a141210b23b6e
X-Runtime: 0.079056
X-Rack-Cache: miss

Whois Lookup

Created: 22nd May, 1998
Changed: 25th January, 2018
Expires: 21st May, 2027
Registrar: NAMECHEAP INC
Status: clientTransferProhibited
Nameservers: ns1.digimedia.com
ns2.digimedia.com
ns3.digimedia.com
Owner Name: Internet Admin not for sale
Owner Organization: Reflex Publishing, Inc.
Owner Street: 301 W. Platt Street No. 510
Owner Post Code: 33606
Owner City: Tampa
Owner State: FL
Owner Country: US
Owner Phone: +1.8133544500
Owner Email: admin@reflex.com
Admin Name: Internet Admin not for sale
Admin Organization: Reflex Publishing, Inc.
Admin Street: 301 W. Platt Street No. 510
Admin Post Code: 33606
Admin City: Tampa
Admin State: FL
Admin Country: US
Admin Phone: +1.8133544500
Admin Email: admin@reflex.com
Tech Name: Internet Admin not for sale
Tech Organization: Reflex Publishing, Inc.
Tech Street: 301 W. Platt Street No. 510
Tech Post Code: 33606
Tech City: Tampa
Tech State: FL
Tech Country: US
Tech Phone: +1.8133544500
Tech Email: admin@reflex.com
Full Whois: Domain name: running.com
Registry Domain ID: 5354176_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.namecheap.com
Registrar URL: http://www.namecheap.com
Updated Date: 2018-01-25T17:19:18.00Z
Creation Date: 1998-05-22T04:00:00.00Z
Registrar Registration Expiration Date: 2027-05-21T04:00:00.00Z
Registrar: NAMECHEAP INC
Registrar IANA ID: 1068
Registrar Abuse Contact Email: abuse@namecheap.com
Registrar Abuse Contact Phone: +1.6613102107
Reseller: NAMECHEAP INC
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID:
Registrant Name: Internet Admin not for sale
Registrant Organization: Reflex Publishing, Inc.
Registrant Street: 301 W. Platt Street No. 510
Registrant City: Tampa
Registrant State/Province: FL
Registrant Postal Code: 33606
Registrant Country: US
Registrant Phone: +1.8133544500
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: admin@reflex.com
Registry Admin ID:
Admin Name: Internet Admin not for sale
Admin Organization: Reflex Publishing, Inc.
Admin Street: 301 W. Platt Street No. 510
Admin City: Tampa
Admin State/Province: FL
Admin Postal Code: 33606
Admin Country: US
Admin Phone: +1.8133544500
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: admin@reflex.com
Registry Tech ID:
Tech Name: Internet Admin not for sale
Tech Organization: Reflex Publishing, Inc.
Tech Street: 301 W. Platt Street No. 510
Tech City: Tampa
Tech State/Province: FL
Tech Postal Code: 33606
Tech Country: US
Tech Phone: +1.8133544500
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: admin@reflex.com
Name Server: ns1.digimedia.com
Name Server: ns2.digimedia.com
Name Server: ns3.digimedia.com
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2020-04-29T23:43:49.50Z <<<

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

Nameservers

Name IP Address
ns1.digimedia.com 23.21.242.88
ns2.digimedia.com 23.21.243.119
ns3.digimedia.com 54.241.0.203
Related

Subdomains

Similar Sites

Domain Valuation Snoop Score
active.com
$1,343,835 USD 4/5
americanrunning.org
$264 USD 1/5
pages.com
$10 USD
realrunner.com
0/5
runnersweb.com
$1,498 USD 1/5
All sites similar to running.com

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
running.be
0/5
running.co.nz
0/5
running.events
0/5
running.net
$620 USD

Sites hosted on the same IP address

Domain Valuation Snoop Score
com.org
$2,641 USD 2/5
irs.org
$978 USD 1/5
phil.com
0/5
recipes.com
$1,048 USD 2/5
temp.com
$3,656 USD 2/5
Love W3 Snoop?
Update Now

Recently Updated

airmp3.net
foresee.com
coolmoviez.com
google.com
facebook.com
healthylivingcatalog.com
gx.games
instagram.com
vlxx.moe
moviesshd.com

Recently Viewed

grainemporium.com
gloshippers.com
asahi-mullion.com
wundercounter.com
berusk.com
cashfat.com
drbackup.net
apotheke4all.net
umcbookstore.com
effisys.fr