Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

fountaintire.com

Fountain Tire - Tires, Tire Service and Full Mechanical

Page Load Speed

2 sec in total

First Response

76 ms

Resources Loaded

1.8 sec

Page Rendered

168 ms

fountaintire.com screenshot

About Website

Welcome to fountaintire.com homepage info - get ready to check Fountain Tire best content for Canada right away, or after learning these important things about fountaintire.com

Fountain Tire offers a wide range of tires for Cars, SUVs, Minivans, Trucks, and Trailers, as well as complete automotive service & repairs for all makes & models.

Visit fountaintire.com

Key Findings

We analyzed Fountaintire.com page load time and found that the first response time was 76 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

fountaintire.com performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

10/100

25%

SI (Speed Index)

Value8.4 s

18/100

10%

TBT (Total Blocking Time)

Value1,290 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.094

91/100

15%

TTI (Time to Interactive)

Value20.8 s

2/100

10%

Network Requests Diagram

fountaintire.com

76 ms

www.fountaintire.com

157 ms

screen.css

54 ms

javascripts.js

59 ms

highslide-with-html.js

233 ms

Our browser made a total of 96 requests to load all elements on the main page. We found that 68% of them (65 requests) were addressed to the original Fountaintire.com, 4% (4 requests) were made to Cm.eyereturn.com and 3% (3 requests) were made to Cm.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (902 ms) relates to the external source Sp.analytics.yahoo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 339.4 kB (56%)

Content Size

606.2 kB

After Optimization

266.8 kB

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

HTML Optimization

-78%

Potential reduce by 23.4 kB

  • Original 30.1 kB
  • After minification 24.6 kB
  • After compression 6.7 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 5.5 kB, which is 18% 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 23.4 kB or 78% of the original size.

Image Optimization

-5%

Potential reduce by 10.0 kB

  • Original 183.1 kB
  • After minification 173.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. Fountain Tire images are well optimized though.

JavaScript Optimization

-77%

Potential reduce by 254.0 kB

  • Original 330.4 kB
  • After minification 233.1 kB
  • After compression 76.4 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 254.0 kB or 77% of the original size.

CSS Optimization

-83%

Potential reduce by 52.0 kB

  • Original 62.6 kB
  • After minification 42.8 kB
  • After compression 10.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. Fountaintire.com needs all CSS files to be minified and compressed as it can save up to 52.0 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

83

After Optimization

26

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

Accessibility Review

fountaintire.com accessibility score

80

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 input fields do not have accessible names

High

ARIA toggle fields do not have accessible names

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

fountaintire.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

fountaintire.com SEO score

73

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

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

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

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

Open Graph description is not detected on the main page of Fountain Tire. 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: