9.7 sec in total
180 ms
6.6 sec
2.9 sec
Welcome to runlansing.com homepage info - get ready to check Runlansing best content right away, or after learning these important things about runlansing.com
Start your next run or walk at Playmakers and shop our best sellers
Visit runlansing.comWe analyzed Runlansing.com page load time and found that the first response time was 180 ms and then it took 9.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
runlansing.com performance score
name
value
score
weighting
Value5.8 s
5/100
10%
Value19.1 s
0/100
25%
Value31.6 s
0/100
10%
Value25,580 ms
0/100
30%
Value0.215
58/100
15%
Value56.3 s
0/100
10%
180 ms
149 ms
377 ms
407 ms
1283 ms
Our browser made a total of 118 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Runlansing.com, 68% (80 requests) were made to Playmakers.com and 4% (5 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source Playmakers.com.
Page size can be reduced by 459.0 kB (4%)
10.7 MB
10.2 MB
In fact, the total size of Runlansing.com main page is 10.7 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only a small number of websites need less resources to load. Images take 9.9 MB which makes up the majority of the site volume.
Potential reduce by 287.5 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 287.5 kB or 87% of the original size.
Potential reduce by 154.9 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. Runlansing images are well optimized though.
Potential reduce by 9.0 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.
Potential reduce by 7.6 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Runlansing.com has all CSS files already compressed.
Number of requests can be reduced by 57 (55%)
103
46
The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Runlansing. 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.
runlansing.com
180 ms
www.playmakers.com
149 ms
www.playmakers.com
377 ms
gtm.js
407 ms
js
1283 ms
slick.min.css
678 ms
slick-theme.min.css
674 ms
slick.eot
677 ms
style.min.css
220 ms
bb-plugin.min.css
215 ms
style.min.css
217 ms
css
385 ms
all.min.css
190 ms
6572-layout.css
616 ms
dashicons.min.css
359 ms
bcd308fb50fad5599ff4c68e48b70a39-layout-bundle.css
358 ms
search-filter.min.css
357 ms
astra-addon-632b38a312ad91-58068410.css
467 ms
3812-layout-partial.css
594 ms
style.css
635 ms
css
612 ms
jquery.min.js
1084 ms
jquery-migrate.min.js
1083 ms
imagesloaded.min.js
634 ms
bb-frontend-search-filter.js
1241 ms
search-filter-build.min.js
1314 ms
chosen.jquery.min.js
1331 ms
main.css
1316 ms
6630-layout-partial.css
1303 ms
6570-layout-partial.css
1580 ms
6595-layout-partial.css
1367 ms
slick.min.js
1264 ms
wc4za4lcmcpaxdbvnkuknvirrni43vgh.js
2196 ms
signup-form-widget.min.js
1295 ms
api.min.js
1120 ms
style.min.js
1569 ms
jquery-carousel.js
1587 ms
imagesloaded.min.js
1564 ms
6572-layout.js
1569 ms
jquery.ba-throttle-debounce.min.js
1587 ms
65309ca30bc98a15a84711ba278191f8-layout-bundle.js
2190 ms
core.min.js
2193 ms
datepicker.min.js
2188 ms
astra-addon-632b38a31398c3-49226453.js
2187 ms
3812-layout-partial.js
2259 ms
main.js
2187 ms
6630-layout-partial.js
2258 ms
6570-layout-partial.js
2238 ms
6595-layout-partial.js
2270 ms
conversion_async.js
1708 ms
analytics.js
1098 ms
js
842 ms
wp-emoji-release.min.js
1570 ms
scl-2021.svg
992 ms
playmakers-logo-2021.svg
1015 ms
pixel.png
1028 ms
Homepage-Banners-2.png
1522 ms
Team-Playmakers-Homepage.png
1013 ms
Monthly-at-LBC-640-%C3%97-480-px.png
1592 ms
Untitled-500-%C3%97-100-px.png
1369 ms
Garmin-Forerunner-255.png
1593 ms
Roll-Recovery-R1-Percussion.png
1394 ms
UCAN-Hydrate-Jar.png
1521 ms
Untitled-design-26-1.png
2291 ms
Goodr-Marvel.png
1878 ms
ON-Cloudgo.jpg
1625 ms
The-North-Face-Borealis-Sling.png
2574 ms
XACT-Wafer-Bar.png
1877 ms
Mens-R1%C2%AE-Daily-Jacket.png
2456 ms
Hoka-Challenger-ATR-6.png
2574 ms
Brooks-Spartan-Semi-Fitted-Running-Pant.png
2456 ms
Oboz-Sawtooth-X-Low-Waterproof.png
2500 ms
Carve-Designs-Carson-Jean.png
2648 ms
bxe_core.js
1317 ms
style.css
1316 ms
embed
847 ms
fbevents.js
847 ms
zaius-min.js
1213 ms
Topo-Ultrafly-4.png
2299 ms
Patagonia-Better-Sweater%C2%AE-1-4-Zip-Fleece.png
2299 ms
Sorel-Out-N-About-III-Low-Sneaker.png
2424 ms
2.png
3085 ms
3.png
2422 ms
4.png
2400 ms
social-icons.png
1055 ms
collect
486 ms
collect
702 ms
5.png
1832 ms
6.png
1834 ms
Shop-Running-1.png
1836 ms
render.64874ea49214d2736b46.js
974 ms
Shop-Running.png
2213 ms
Shop-Running-2.png
1835 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
1370 ms
wARDj0u
81 ms
tDbM2oWUg0MKoZw1-LPK9Q.woff
1534 ms
1607 ms
LeagueSpartan-Bold.ttf
2069 ms
AvenirLTStd-Black.ttf
1767 ms
fa-brands-400.woff
2096 ms
js
1474 ms
fa-solid-900.woff
2111 ms
fa-regular-400.woff
2082 ms
SundayNight-1024x683.jpg
2038 ms
Untitled-2048-%C3%97-1365-px-1000-%C3%97-489-px-4.png
2038 ms
Untitled-2048-%C3%97-1365-px-3.png
2039 ms
411933639695372
429 ms
Untitled-design-19.png
1872 ms
collect
1214 ms
2022-best-running-stores-Logo.svg
1691 ms
css
234 ms
wurfl.js
1216 ms
RIDC_Logo_Letters_Color_RGB_LG.svg
1568 ms
gen_204
141 ms
90 ms
init_embed.js
652 ms
underscore-min.js
79 ms
1f3c3.svg
317 ms
runlansing.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
runlansing.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
runlansing.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Runlansing.com 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 Runlansing.com 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.
runlansing.com
Open Graph data is detected on the main page of Runlansing. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: