Tools & Wizards About Us
stores.finishline.com screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    55% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

stores.finishline.com

Find a Finish Line Shoe Store Near You

Page Load Speed

415 ms in total

First Response

29 ms

Resources Loaded

318 ms

Page Rendered

68 ms

stores.finishline.com screenshot

About Website

Welcome to stores.finishline.com homepage info - get ready to check Store S Finish Line best content for United States right away, or after learning these important things about stores.finishline.com

Find a Finish Line near you using our store locator. Shop shoes and apparel for the whole family from top brands like Nike, adidas, Jordan, New Balance and more.

Visit stores.finishline.com

Key Findings

We analyzed Stores.finishline.com page load time and found that the first response time was 29 ms and then it took 386 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

stores.finishline.com performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

65/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

47/100

25%

SI (Speed Index)

Value3.4 s

90/100

10%

TBT (Total Blocking Time)

Value1,360 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.469

18/100

15%

TTI (Time to Interactive)

Value14.5 s

8/100

10%

Network Requests Diagram

stores.finishline.com

29 ms

stores.finishline.com

19 ms

gtm.js

81 ms

slick.css

131 ms

client-finishline.css

134 ms

Our browser made a total of 19 requests to load all elements on the main page. We found that 16% of them (3 requests) were addressed to the original Stores.finishline.com, 68% (13 requests) were made to Assets.stores.finishline.com and 5% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (188 ms) relates to the external source Assets.stores.finishline.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 81.5 kB (14%)

Content Size

579.1 kB

After Optimization

497.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Stores.finishline.com main page is 579.1 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. 60% of websites need less resources to load. Javascripts take 342.7 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 68.4 kB

  • Original 80.5 kB
  • After minification 78.0 kB
  • After compression 12.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 68.4 kB or 85% of the original size.

Image Optimization

-1%

Potential reduce by 87 B

  • Original 7.2 kB
  • After minification 7.1 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. Store S Finish Line images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 8.8 kB

  • Original 342.7 kB
  • After minification 342.7 kB
  • After compression 333.9 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.

CSS Optimization

-3%

Potential reduce by 4.1 kB

  • Original 148.7 kB
  • After minification 148.7 kB
  • After compression 144.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. Stores.finishline.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 9 (60%)

Requests Now

15

After Optimization

6

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

stores.finishline.com

stores.finishline.com

29 ms

stores.finishline.com

stores.finishline.com

19 ms

gtm.js

gtm.js

81 ms

slick.css

slick.css

131 ms

client-finishline.css

client-finishline.css

134 ms

styles.min.css

styles.min.css

147 ms

pollyfill.min.js

pollyfill.min.js

131 ms

leaflet.js

leaflet.js

146 ms

js

js

67 ms

Leaflet.GoogleMutant.js

Leaflet.GoogleMutant.js

132 ms

page.js

page.js

146 ms

locator.js

locator.js

146 ms

scripts.min.js

scripts.min.js

188 ms

slick.js

slick.js

187 ms

client-finishline.js

client-finishline.js

187 ms

logo-fl-header.png

logo-fl-header.png

57 ms

getAutocompleteData

getAutocompleteData

32 ms

Knockout.woff

Knockout.woff

13 ms

Tf4LE6lHog==

Tf4LE6lHog==

12 ms

Accessibility Review

stores.finishline.com accessibility score

83

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

Best Practices

stores.finishline.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

stores.finishline.com SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

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 Stores.finishline.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 Stores.finishline.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.

Social Sharing Optimization

stores.finishline.com

Open Graph description is not detected on the main page of Store S Finish Line. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: