Tools & Wizards About Us
firestonetires.com screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

firestonetires.com

New Tires for Trucks, Cars, SUVs & Minivans | Firestone Tires

Page Load Speed

10.3 sec in total

First Response

477 ms

Resources Loaded

8.6 sec

Page Rendered

1.2 sec

firestonetires.com screenshot

About Website

Visit firestonetires.com now to see the best up-to-date Firestone Tires content and also check out these interesting facts you probably never knew about firestonetires.com

Firestone Tires offers specialized tires for any vehicle and any time of year. Discover our tire brands to find the ideal tire for your car, truck or SUV.

Visit firestonetires.com

Key Findings

We analyzed Firestonetires.com page load time and found that the first response time was 477 ms and then it took 9.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

firestonetires.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

19/100

25%

SI (Speed Index)

Value9.8 s

10/100

10%

TBT (Total Blocking Time)

Value2,160 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.307

38/100

15%

TTI (Time to Interactive)

Value18.1 s

3/100

10%

Network Requests Diagram

firestonetires.com

477 ms

www.firestonetire.com

5042 ms

ruxitagentjs_ICANVfqrux_10297240712040816.js

51 ms

launch-033b3f120756.min.js

19 ms

v1.min.css

14 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Firestonetires.com, 48% (19 requests) were made to Assets.firestonetire.com and 38% (15 requests) were made to Firestonetire.com. The less responsive or slowest element that took the longest time to load (5 sec) relates to the external source Firestonetire.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 97.4 kB (9%)

Content Size

1.1 MB

After Optimization

958.0 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Firestonetires.com main page is 1.1 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. 25% of websites need less resources to load. Images take 821.5 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 97.3 kB

  • Original 110.8 kB
  • After minification 86.4 kB
  • After compression 13.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. This page needs HTML code to be minified as it can gain 24.4 kB, which is 22% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 97.3 kB or 88% of the original size.

Image Optimization

-0%

Potential reduce by 13 B

  • Original 821.5 kB
  • After minification 821.5 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. Firestone Tires images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 23 B

  • Original 123.1 kB
  • After minification 123.1 kB
  • After compression 123.1 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 26 (70%)

Requests Now

37

After Optimization

11

  • Images
  • JavaScript
  • CSS

The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Firestone Tires. 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 from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

firestonetires.com

firestonetires.com

477 ms

www.firestonetire.com

www.firestonetire.com

5042 ms

ruxitagentjs_ICANVfqrux_10297240712040816.js

ruxitagentjs_ICANVfqrux_10297240712040816.js

51 ms

launch-033b3f120756.min.js

launch-033b3f120756.min.js

19 ms

v1.min.css

v1.min.css

14 ms

v1.min.css

v1.min.css

33 ms

v1.min.css

v1.min.css

30 ms

v1.min.css

v1.min.css

23 ms

clientlibs.min.js

clientlibs.min.js

20 ms

v1.min.js

v1.min.js

24 ms

container.min.js

container.min.js

31 ms

v1.min.js

v1.min.js

46 ms

v1.min.js

v1.min.js

133 ms

v1.min.js

v1.min.js

39 ms

snare.js

snare.js

17 ms

firestone-shield.svg

firestone-shield.svg

70 ms

usa.jpg

usa.jpg

217 ms

logo.js

logo.js

41 ms

canada.jpg

canada.jpg

81 ms

destination-mt2-hero-1170.jpg

destination-mt2-hero-1170.jpg

545 ms

hero.png

hero.png

201 ms

hero.jpg

hero.jpg

247 ms

hero.jpg

hero.jpg

763 ms

hero.jpg

hero.jpg

423 ms

hero.jpg

hero.jpg

386 ms

hero.jpg

hero.jpg

293 ms

hero.jpg

hero.jpg

418 ms

hero.jpg

hero.jpg

428 ms

hero.jpg

hero.jpg

707 ms

hero.jpg

hero.jpg

896 ms

hero.jpg

hero.jpg

808 ms

hero.jpg

hero.jpg

583 ms

hero.jpg

hero.jpg

727 ms

hero.jpg

hero.jpg

788 ms

hero.jpg

hero.jpg

1088 ms

hero.jpg

hero.jpg

2884 ms

firestone-logo.svg

firestone-logo.svg

845 ms

topographic-bg.jpg

topographic-bg.jpg

30 ms

bg-texture.jpg

bg-texture.jpg

75 ms

common-consumer-icons.ttf

common-consumer-icons.ttf

11 ms

Accessibility Review

firestonetires.com accessibility score

90

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

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

firestonetires.com 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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

firestonetires.com SEO score

93

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

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

firestonetires.com

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