Tools & Wizards About Us
frisbytire.com screenshot

Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

frisbytire.com

Frisby Tire | Summer, Winter, All Season and Performance Tire Center

Page Load Speed

2.9 sec in total

First Response

58 ms

Resources Loaded

2.4 sec

Page Rendered

510 ms

frisbytire.com screenshot

About Website

Visit frisbytire.com now to see the best up-to-date Frisby Tire content for Canada and also check out these interesting facts you probably never knew about frisbytire.com

Frisby Tire stores are transitioning to Kal Tire locations. During this time, you'll continue to receive expert advice and service at any of our 5 locations across Ottawa.

Visit frisbytire.com

Key Findings

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

Performance Metrics

frisbytire.com performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value12.0 s

0/100

25%

SI (Speed Index)

Value9.3 s

12/100

10%

TBT (Total Blocking Time)

Value1,610 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value1.166

1/100

15%

TTI (Time to Interactive)

Value22.7 s

1/100

10%

Network Requests Diagram

frisbytire.com

58 ms

kaltire.com

341 ms

www.kaltire.com

542 ms

font-awesome.min.css

41 ms

fonts.css

37 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Frisbytire.com, 66% (38 requests) were made to Kaltire.com and 14% (8 requests) were made to . The less responsive or slowest element that took the longest time to load (542 ms) relates to the external source Kaltire.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 252.3 kB (13%)

Content Size

2.0 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-87%

Potential reduce by 206.4 kB

  • Original 236.7 kB
  • After minification 236.6 kB
  • After compression 30.3 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 206.4 kB or 87% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 267.1 kB
  • After minification 267.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. Frisby Tire images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 45.0 kB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 1.3 MB

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

-0%

Potential reduce by 879 B

  • Original 206.1 kB
  • After minification 206.1 kB
  • After compression 205.3 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. Frisbytire.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 28 (62%)

Requests Now

45

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

frisbytire.com

frisbytire.com

58 ms

kaltire.com

kaltire.com

341 ms

www.kaltire.com

www.kaltire.com

542 ms

font-awesome.min.css

font-awesome.min.css

41 ms

fonts.css

fonts.css

37 ms

app.css

app.css

57 ms

jquery-2.2.5.min.js

jquery-2.2.5.min.js

32 ms

jquery-ui.min.js

jquery-ui.min.js

37 ms

slick.min.js

slick.min.js

34 ms

jquery.jcarousel.min.js

jquery.jcarousel.min.js

34 ms

jquery.validate.min.js

jquery.validate.min.js

37 ms

jquery.zoom.min.js

jquery.zoom.min.js

44 ms

jquery.cookie.min.js

jquery.cookie.min.js

59 ms

underscore-min.js

underscore-min.js

92 ms

moment.min.js

moment.min.js

59 ms

clndr.min.js

clndr.min.js

64 ms

foundation.js

foundation.js

56 ms

jquery.smooth-scroll.js

jquery.smooth-scroll.js

64 ms

js

js

95 ms

infobox.min.js

infobox.min.js

72 ms

app.js

app.js

104 ms

api.js

api.js

56 ms

ui.js

ui.js

36 ms

gtm.js

gtm.js

86 ms

dwanalytics-22.2.js

dwanalytics-22.2.js

79 ms

dwac-21.7.js

dwac-21.7.js

85 ms

gretel.min.js

gretel.min.js

37 ms

12BA994CA9150E4DD.css

12BA994CA9150E4DD.css

536 ms

logo@2x.png

logo@2x.png

203 ms

NAV-Price-Match-Guarantee.png

NAV-Price-Match-Guarantee.png

170 ms

NAV-Warranty.png

NAV-Warranty.png

166 ms

NAV-Winter-Tire-Change.png

NAV-Winter-Tire-Change.png

167 ms

find-tire-size-image.jpg

find-tire-size-image.jpg

171 ms

Car.jpg

Car.jpg

168 ms

Tire.jpg

Tire.jpg

167 ms

Truck.jpg

Truck.jpg

171 ms

Wheel.jpg

Wheel.jpg

176 ms

packages.png

packages.png

171 ms

Left-Home-Brake-Check.jpg

Left-Home-Brake-Check.jpg

171 ms

Home-Right-Nokian.png

Home-Right-Nokian.png

173 ms

KT-NHL-Lockup_KT-NHL-Lockup.png

KT-NHL-Lockup_KT-NHL-Lockup.png

174 ms

KT-NHL-Lockup_KT-NHL-Lockup-small.png

KT-NHL-Lockup_KT-NHL-Lockup-small.png

173 ms

qd+TGu6XJzLwK3qzzXKYeqc+L442CIxHdRkZdbYGaLU7ja73I7tkXbsoSEVVPlx0npf49NDVoVqeB3n9HbGVFAc=

qd+TGu6XJzLwK3qzzXKYeqc+L442CIxHdRkZdbYGaLU7ja73I7tkXbsoSEVVPlx0npf49NDVoVqeB3n9HbGVFAc=

13 ms

R2xlRQH

R2xlRQH

13 ms

R2xlRQH

R2xlRQH

12 ms

j00NWhWp4Hef0dsZUUBw==

j00NWhWp4Hef0dsZUUBw==

12 ms

fontello.woff

fontello.woff

353 ms

j00NWhWp4Hef0dsZUUBw==

j00NWhWp4Hef0dsZUUBw==

11 ms

j00NWhWp4Hef0dsZUUBw==

j00NWhWp4Hef0dsZUUBw==

11 ms

j00NWhWp4Hef0dsZUUBw==

j00NWhWp4Hef0dsZUUBw==

9 ms

R2xlRQH

R2xlRQH

9 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

532 ms

include.js

include.js

134 ms

gtm.js

gtm.js

131 ms

recaptcha__en.js

recaptcha__en.js

43 ms

inside.js

inside.js

34 ms

ig.js

ig.js

27 ms

config

config

79 ms

Accessibility Review

frisbytire.com accessibility score

83

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

frisbytire.com best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

frisbytire.com SEO score

86

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

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

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

frisbytire.com

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