Tools & Wizards About Us
mbcollision.ca screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 38

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

mbcollision.ca

Certified Repair Facility | Mercedes-Benz Collision Centre

Page Load Speed

1.9 sec in total

First Response

183 ms

Resources Loaded

1.6 sec

Page Rendered

129 ms

mbcollision.ca screenshot

About Website

Click here to check amazing Mb Collision content. Otherwise, check out these important facts you probably never knew about mbcollision.ca

We are a Mercedes Benz certified collision repair facility. Trust our factory-certiifed technicians to restore the beauty of your vehicle. Book online today!

Visit mbcollision.ca

Key Findings

We analyzed Mbcollision.ca page load time and found that the first response time was 183 ms and then it took 1.7 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

mbcollision.ca performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

17/100

10%

LCP (Largest Contentful Paint)

Value8.5 s

1/100

25%

SI (Speed Index)

Value5.3 s

57/100

10%

TBT (Total Blocking Time)

Value320 ms

77/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.7 s

56/100

10%

Network Requests Diagram

mbcollision.ca

183 ms

mbcollision.ca

378 ms

js

59 ms

styles-mb-map.css

88 ms

stylesheet.css

156 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 88% of them (43 requests) were addressed to the original Mbcollision.ca, 4% (2 requests) were made to Ajax.googleapis.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (609 ms) belongs to the original domain Mbcollision.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 178.7 kB (8%)

Content Size

2.2 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mbcollision.ca main page is 2.2 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. 30% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 33.6 kB

  • Original 42.9 kB
  • After minification 39.6 kB
  • After compression 9.2 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 33.6 kB or 78% of the original size.

Image Optimization

-4%

Potential reduce by 73.1 kB

  • Original 1.9 MB
  • After minification 1.8 MB

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. Mb Collision images are well optimized though.

JavaScript Optimization

-35%

Potential reduce by 69.5 kB

  • Original 198.0 kB
  • After minification 197.7 kB
  • After compression 128.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 69.5 kB or 35% of the original size.

CSS Optimization

-23%

Potential reduce by 2.4 kB

  • Original 10.4 kB
  • After minification 10.4 kB
  • After compression 8.0 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. Mbcollision.ca needs all CSS files to be minified and compressed as it can save up to 2.4 kB or 23% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (37%)

Requests Now

46

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mbcollision.ca

mbcollision.ca

183 ms

mbcollision.ca

mbcollision.ca

378 ms

js

js

59 ms

styles-mb-map.css

styles-mb-map.css

88 ms

stylesheet.css

stylesheet.css

156 ms

jquery.min.js

jquery.min.js

19 ms

jquery.scrollTo-1.4.2-min.js

jquery.scrollTo-1.4.2-min.js

230 ms

waypoints.min.js

waypoints.min.js

228 ms

navbar2.js

navbar2.js

231 ms

jquery-ui.min.js

jquery-ui.min.js

22 ms

jquery.mousewheel-3.0.6.pack.js

jquery.mousewheel-3.0.6.pack.js

247 ms

jquery.fancybox.js

jquery.fancybox.js

319 ms

jquery.fancybox.css

jquery.fancybox.css

247 ms

vimeostyle.css

vimeostyle.css

301 ms

vimeo.resize.js

vimeo.resize.js

304 ms

skdslider.js

skdslider.js

305 ms

skdslider.css

skdslider.css

313 ms

owl.carousel.js

owl.carousel.js

322 ms

owl.carousel.css

owl.carousel.css

374 ms

owl.theme.css

owl.theme.css

380 ms

analytics.js

analytics.js

19 ms

collect

collect

12 ms

lato-light-webfont.woff

lato-light-webfont.woff

214 ms

154220025

154220025

149 ms

AjaxLoader.gif

AjaxLoader.gif

84 ms

mb-logo.svg

mb-logo.svg

85 ms

header-shadow.png

header-shadow.png

81 ms

spacer.gif

spacer.gif

84 ms

85_semi_white.png

85_semi_white.png

83 ms

mb-map2.png

mb-map2.png

406 ms

1.png

1.png

302 ms

2.png

2.png

308 ms

3.png

3.png

238 ms

4.png

4.png

387 ms

5.png

5.png

313 ms

6.png

6.png

394 ms

7.png

7.png

450 ms

8.png

8.png

383 ms

9.png

9.png

465 ms

10.png

10.png

534 ms

11.png

11.png

539 ms

silver-metal-bg.jpg

silver-metal-bg.jpg

474 ms

dotted-bg.png

dotted-bg.png

481 ms

contact-icon.png

contact-icon.png

524 ms

location-icon.png

location-icon.png

542 ms

social-media-icon.png

social-media-icon.png

551 ms

fb-icon.png

fb-icon.png

556 ms

linkedin-icon.png

linkedin-icon.png

599 ms

mblogo_small.png

mblogo_small.png

609 ms

Accessibility Review

mbcollision.ca accessibility score

38

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

mbcollision.ca SEO score

83

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mbcollision.ca can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Mbcollision.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

mbcollision.ca

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