Tools & Wizards About Us
collisiontroy.com screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    71% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

collisiontroy.com

Troy, MI Auto Body Repair Services - The Collision Shop Troy North

Page Load Speed

2.3 sec in total

First Response

221 ms

Resources Loaded

1.6 sec

Page Rendered

422 ms

collisiontroy.com screenshot

About Website

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

At The Collision Shop Troy North, we will put your vehicle back to pre-accident condition, structurally and cosmetically. Serving Troy, MI we offer full auto body repair services. Call us today to get...

Visit collisiontroy.com

Key Findings

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

Performance Metrics

collisiontroy.com performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.5 s

96/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

27/100

25%

SI (Speed Index)

Value3.1 s

92/100

10%

TBT (Total Blocking Time)

Value410 ms

67/100

30%

CLS (Cumulative Layout Shift)

Value0.61

10/100

15%

TTI (Time to Interactive)

Value5.7 s

68/100

10%

Network Requests Diagram

collisiontroy.com

221 ms

collisiontroy.com

403 ms

js

99 ms

the-collision-shop-troy-north-og-logo.png

135 ms

the-collision-shop-troy-north-banner.jpg

482 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 45% of them (20 requests) were addressed to the original Collisiontroy.com, 52% (23 requests) were made to Codingserver.net and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (728 ms) relates to the external source Codingserver.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 45.0 kB (7%)

Content Size

616.9 kB

After Optimization

571.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-84%

Potential reduce by 40.3 kB

  • Original 47.9 kB
  • After minification 40.7 kB
  • After compression 7.6 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 7.2 kB, which is 15% 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 40.3 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 412.6 kB
  • After minification 412.6 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. Collision Troy images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 2.6 kB

  • Original 131.9 kB
  • After minification 131.9 kB
  • After compression 129.2 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.

CSS Optimization

-8%

Potential reduce by 2.0 kB

  • Original 24.5 kB
  • After minification 24.5 kB
  • After compression 22.5 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. Collisiontroy.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 20 (54%)

Requests Now

37

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

collisiontroy.com

collisiontroy.com

221 ms

collisiontroy.com

collisiontroy.com

403 ms

js

js

99 ms

the-collision-shop-troy-north-og-logo.png

the-collision-shop-troy-north-og-logo.png

135 ms

the-collision-shop-troy-north-banner.jpg

the-collision-shop-troy-north-banner.jpg

482 ms

service-paint.jpg

service-paint.jpg

297 ms

icon-paint.png

icon-paint.png

316 ms

service-collision.jpg

service-collision.jpg

298 ms

icon-collision.png

icon-collision.png

316 ms

service-auto-glass.jpg

service-auto-glass.jpg

363 ms

icon-glass.png

icon-glass.png

360 ms

service-fleet.jpg

service-fleet.jpg

360 ms

icon-fleet.png

icon-fleet.png

378 ms

service-detailing.jpg

service-detailing.jpg

440 ms

icon-detailing.png

icon-detailing.png

422 ms

service-frame.jpg

service-frame.jpg

424 ms

icon-frame.png

icon-frame.png

426 ms

style.css

style.css

435 ms

responsive.css

responsive.css

479 ms

font-awesome.css

font-awesome.css

469 ms

liafont.css

liafont.css

481 ms

default-fonts.css

default-fonts.css

480 ms

jquery.min.js

jquery.min.js

543 ms

jquery-ui.js

jquery-ui.js

608 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

481 ms

jquery-ui-1.10.1.custom.css

jquery-ui-1.10.1.custom.css

532 ms

jquery.mousewheel.min2.js

jquery.mousewheel.min2.js

556 ms

jquery.simplr.smoothscroll.js

jquery.simplr.smoothscroll.js

558 ms

style.css

style.css

603 ms

jquery.dropdownPlain.js

jquery.dropdownPlain.js

595 ms

jquery.viewport.mini.js

jquery.viewport.mini.js

605 ms

prettyPhoto.css

prettyPhoto.css

668 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

623 ms

carouFredSel.js

carouFredSel.js

661 ms

script.php

script.php

725 ms

style.css

style.css

728 ms

script.js

script.js

479 ms

custom.css

custom.css

479 ms

133 ms

OpenSans.woff

OpenSans.woff

65 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

131 ms

OpenSans-ExtraBold.woff

OpenSans-ExtraBold.woff

126 ms

OpenSans-Bold.woff

OpenSans-Bold.woff

130 ms

liafont.woff

liafont.woff

69 ms

Accessibility Review

collisiontroy.com accessibility score

96

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

Heading elements are not in a sequentially-descending order

Best Practices

collisiontroy.com best practices score

83

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

collisiontroy.com SEO score

93

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

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

collisiontroy.com

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