Report Summary

  • 84

    Performance

    Renders faster than
    88% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 79% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

Page Load Speed

4.2 sec in total

First Response

793 ms

Resources Loaded

3.2 sec

Page Rendered

145 ms

torontoparts.ca screenshot

About Website

Click here to check amazing Torontoparts content. Otherwise, check out these important facts you probably never knew about torontoparts.ca

Welcome to TorontoParts.ca , your one stop for auto Part Store! Selling quality OEM parts in Toronto for most porsche, bmw, audi, mercedes benz, volvo, mini

Visit torontoparts.ca

Key Findings

We analyzed Torontoparts.ca page load time and found that the first response time was 793 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

torontoparts.ca performance score

84

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

64/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

56/100

25%

SI (Speed Index)

Value2.6 s

97/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.046

99/100

15%

TTI (Time to Interactive)

Value3.1 s

95/100

10%

Network Requests Diagram

www.torontoparts.ca

793 ms

wp-emoji-release.min.js

203 ms

styles.css

242 ms

swfobject.js

7 ms

jquery.js

298 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 42% of them (25 requests) were addressed to the original Torontoparts.ca, 22% (13 requests) were made to Maps.googleapis.com and 12% (7 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (969 ms) belongs to the original domain Torontoparts.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 640.7 kB (65%)

Content Size

991.7 kB

After Optimization

350.9 kB

In fact, the total size of Torontoparts.ca main page is 991.7 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. 50% of websites need less resources to load. Javascripts take 865.5 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 15.7 kB

  • Original 20.8 kB
  • After minification 17.9 kB
  • After compression 5.1 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 2.9 kB, which is 14% 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 15.7 kB or 76% of the original size.

Image Optimization

-3%

Potential reduce by 2.4 kB

  • Original 70.2 kB
  • After minification 67.8 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. Torontoparts images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 594.6 kB

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

CSS Optimization

-80%

Potential reduce by 28.0 kB

  • Original 35.2 kB
  • After minification 31.1 kB
  • After compression 7.2 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. Torontoparts.ca needs all CSS files to be minified and compressed as it can save up to 28.0 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 36 (68%)

Requests Now

53

After Optimization

17

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

Accessibility Review

torontoparts.ca accessibility score

92

Accessibility Issues

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

Links do not have a discernible name

Best Practices

torontoparts.ca 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

torontoparts.ca SEO score

100

Search Engine Optimization Advices

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

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Torontoparts.ca can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Torontoparts.ca 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 Torontoparts. 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: