Tools & Wizards About Us
runtrails.org screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

runtrails.org

Run Trails

Page Load Speed

7.1 sec in total

First Response

271 ms

Resources Loaded

1.4 sec

Page Rendered

5.5 sec

runtrails.org screenshot

About Website

Visit runtrails.org now to see the best up-to-date Run Trails content for United States and also check out these interesting facts you probably never knew about runtrails.org

Trail running is not only fun but also keeps you fit. You can consider this sport as part of your personal workout plan or train on trails as preparation for competition.

Visit runtrails.org

Key Findings

We analyzed Runtrails.org page load time and found that the first response time was 271 ms and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

runtrails.org performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value9.8 s

0/100

25%

SI (Speed Index)

Value7.4 s

28/100

10%

TBT (Total Blocking Time)

Value2,310 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.012

100/100

15%

TTI (Time to Interactive)

Value13.3 s

12/100

10%

Network Requests Diagram

runtrails.org

271 ms

runtrails.org

325 ms

wp-emoji-release.min.js

114 ms

style.min.css

130 ms

classic-themes.min.css

154 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 76% of them (56 requests) were addressed to the original Runtrails.org, 8% (6 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (388 ms) belongs to the original domain Runtrails.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 397.7 kB (52%)

Content Size

767.0 kB

After Optimization

369.4 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Runtrails.org main page is 767.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. HTML takes 436.2 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 389.1 kB

  • Original 436.2 kB
  • After minification 427.1 kB
  • After compression 47.0 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 389.1 kB or 89% of the original size.

Image Optimization

-3%

Potential reduce by 8.2 kB

  • Original 304.9 kB
  • After minification 296.7 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Run Trails images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 358 B

  • Original 26.0 kB
  • After minification 25.9 kB
  • After compression 25.6 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 57 (89%)

Requests Now

64

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Run Trails. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

runtrails.org

runtrails.org

271 ms

runtrails.org

runtrails.org

325 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

114 ms

style.min.css

style.min.css

130 ms

classic-themes.min.css

classic-themes.min.css

154 ms

screen.min.css

screen.min.css

101 ms

style.min.css

style.min.css

115 ms

theme.min.css

theme.min.css

133 ms

elementor-icons.min.css

elementor-icons.min.css

134 ms

frontend-legacy.min.css

frontend-legacy.min.css

143 ms

frontend.min.css

frontend.min.css

163 ms

swiper.min.css

swiper.min.css

153 ms

post-353.css

post-353.css

169 ms

frontend.min.css

frontend.min.css

233 ms

post-74.css

post-74.css

217 ms

post-196.css

post-196.css

181 ms

post-435.css

post-435.css

185 ms

css-protect.css

css-protect.css

196 ms

print-protection.css

print-protection.css

197 ms

css

css

47 ms

fontawesome.min.css

fontawesome.min.css

217 ms

solid.min.css

solid.min.css

216 ms

brands.min.css

brands.min.css

246 ms

jquery.min.js

jquery.min.js

221 ms

jquery-migrate.min.js

jquery-migrate.min.js

241 ms

run-trails.js

run-trails.js

68 ms

js

js

81 ms

affiliate_app_confirm.php

affiliate_app_confirm.php

31 ms

snippet.min.js

snippet.min.js

66 ms

DMCABadgeHelper.min.js

DMCABadgeHelper.min.js

85 ms

animations.min.css

animations.min.css

380 ms

dynamic-conditions-public.js

dynamic-conditions-public.js

380 ms

frontend.min.js

frontend.min.js

378 ms

admin_bar_ajax.js

admin_bar_ajax.js

380 ms

smush-lazy-load-native.min.js

smush-lazy-load-native.min.js

380 ms

OneSignalSDK.js

OneSignalSDK.js

52 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

382 ms

imagesloaded.min.js

imagesloaded.min.js

382 ms

js.cookie.min.js

js.cookie.min.js

385 ms

jquery.sticky-kit.min.js

jquery.sticky-kit.min.js

382 ms

front.min.js

front.min.js

382 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

388 ms

webpack.runtime.min.js

webpack.runtime.min.js

384 ms

frontend-modules.min.js

frontend-modules.min.js

385 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

384 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

296 ms

wp-polyfill.min.js

wp-polyfill.min.js

285 ms

hooks.min.js

hooks.min.js

283 ms

i18n.min.js

i18n.min.js

268 ms

frontend.min.js

frontend.min.js

266 ms

waypoints.min.js

waypoints.min.js

299 ms

core.min.js

core.min.js

257 ms

swiper.min.js

swiper.min.js

249 ms

share-link.min.js

share-link.min.js

384 ms

dialog.min.js

dialog.min.js

266 ms

frontend.min.js

frontend.min.js

265 ms

preloaded-elements-handlers.min.js

preloaded-elements-handlers.min.js

355 ms

preloaded-modules.min.js

preloaded-modules.min.js

248 ms

jquery.sticky.min.js

jquery.sticky.min.js

237 ms

gtm.js

gtm.js

130 ms

dmca_protected_sml_120n.png

dmca_protected_sml_120n.png

81 ms

cropped-men-running-in-trails.jpg

cropped-men-running-in-trails.jpg

240 ms

js

js

144 ms

analytics.js

analytics.js

124 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

139 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

237 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

283 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

313 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

313 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

313 ms

fa-solid-900.woff

fa-solid-900.woff

137 ms

fa-brands-400.woff

fa-brands-400.woff

282 ms

cropped-Run-Trails-logo-p51q75ghqg0fev020zwdbmauuutrxrd7d74aq0nhfk.png

cropped-Run-Trails-logo-p51q75ghqg0fev020zwdbmauuutrxrd7d74aq0nhfk.png

235 ms

collect

collect

106 ms

Accessibility Review

runtrails.org accessibility score

96

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

<frame> or <iframe> elements do not have a title

Best Practices

runtrails.org best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

runtrails.org SEO score

97

Search Engine Optimization Advices

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Runtrails.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Runtrails.org main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

runtrails.org

Open Graph data is detected on the main page of Run Trails. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: