Tools & Wizards About Us
critz.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

critz.com

Critz Auto Savannah | Hilton Head | Statesboro | Dealer Group | Cars For Sale

Page Load Speed

2.9 sec in total

First Response

389 ms

Resources Loaded

2.2 sec

Page Rendered

315 ms

critz.com screenshot

About Website

Welcome to critz.com homepage info - get ready to check Critz best content for United States right away, or after learning these important things about critz.com

Visit Critz Auto for all of your automotive needs in Savannah, GA. Shop cars for sale, browse lease deals, or schedule service.

Visit critz.com

Key Findings

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

Performance Metrics

critz.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value30.7 s

0/100

25%

SI (Speed Index)

Value10.7 s

7/100

10%

TBT (Total Blocking Time)

Value14,470 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value37.7 s

0/100

10%

Network Requests Diagram

www.critz.com

389 ms

blue_white.css

384 ms

type.css

231 ms

blue_white-widgets.css

548 ms

custom.css

117 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 80% of them (61 requests) were addressed to the original Critz.com, 5% (4 requests) were made to Pictures.dealer.com and 5% (4 requests) were made to Static.dealer.com. The less responsive or slowest element that took the longest time to load (744 ms) belongs to the original domain Critz.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (53%)

Content Size

2.7 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 327.3 kB

  • Original 409.9 kB
  • After minification 405.5 kB
  • After compression 82.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. 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 327.3 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 874 B

  • Original 416.4 kB
  • After minification 415.5 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. Critz images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 1.0 MB

  • Original 1.7 MB
  • After minification 1.7 MB
  • After compression 650.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 1.0 MB or 61% of the original size.

CSS Optimization

-34%

Potential reduce by 52.4 kB

  • Original 155.5 kB
  • After minification 155.5 kB
  • After compression 103.1 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. Critz.com needs all CSS files to be minified and compressed as it can save up to 52.4 kB or 34% of the original size.

Requests Breakdown

Number of requests can be reduced by 66 (89%)

Requests Now

74

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.critz.com

www.critz.com

389 ms

blue_white.css

blue_white.css

384 ms

type.css

type.css

231 ms

blue_white-widgets.css

blue_white-widgets.css

548 ms

custom.css

custom.css

117 ms

ldclient.min.js

ldclient.min.js

19 ms

pix-ddc-fp.min.js

pix-ddc-fp.min.js

443 ms

blocker.js

blocker.js

72 ms

phone-swapping.min.js

phone-swapping.min.js

43 ms

ddc.jquery.async.each.min.js

ddc.jquery.async.each.min.js

65 ms

ddc.min.js

ddc.min.js

540 ms

ddc-core-js-polyfills.min.js

ddc-core-js-polyfills.min.js

109 ms

react.production.min.js

react.production.min.js

125 ms

react-dom.production.min.js

react-dom.production.min.js

141 ms

prop-types.min.js

prop-types.min.js

164 ms

react-bootstrap.min.js

react-bootstrap.min.js

181 ms

redux.min.js

redux.min.js

196 ms

react-redux.min.js

react-redux.min.js

212 ms

redux-thunk.min.js

redux-thunk.min.js

219 ms

redux-toolkit.umd.min.js

redux-toolkit.umd.min.js

228 ms

html-react-parser.min.js

html-react-parser.min.js

233 ms

umd.js

umd.js

242 ms

hysterics.js

hysterics.js

248 ms

loader.js

loader.js

257 ms

widget.min.js

widget.min.js

314 ms

data-layer-helper.min.js

data-layer-helper.min.js

324 ms

widget.min.js

widget.min.js

339 ms

widget.min.js

widget.min.js

355 ms

widget.min.js

widget.min.js

398 ms

bundle.c18ea3a76af385ffe7c87f35c6f7c4e5.js

bundle.c18ea3a76af385ffe7c87f35c6f7c4e5.js

621 ms

bundle.6df13fa18f853a074edc44c05fa90149.js

bundle.6df13fa18f853a074edc44c05fa90149.js

380 ms

lib.js

lib.js

401 ms

pubsub.min.js

pubsub.min.js

413 ms

eo.min.js

eo.min.js

453 ms

userProfileController.min.js

userProfileController.min.js

461 ms

bundle.421e099d72c3ea25f5386bd7d2133b00.js

bundle.421e099d72c3ea25f5386bd7d2133b00.js

470 ms

bundle.de647c6a44b1c3f4b7ddfe7f0aecb9ac.js

bundle.de647c6a44b1c3f4b7ddfe7f0aecb9ac.js

469 ms

bundle.fff9c5dc121a271ebb5a0a40a2a0bf12.js

bundle.fff9c5dc121a271ebb5a0a40a2a0bf12.js

475 ms

ftm-ddc.js

ftm-ddc.js

58 ms

bundle.4e90e6fea33cebd2744cef9d5a66d3c3.js

bundle.4e90e6fea33cebd2744cef9d5a66d3c3.js

482 ms

jquery.inview.min.js

jquery.inview.min.js

744 ms

tab.min.js

tab.min.js

474 ms

slick.min.js

slick.min.js

605 ms

widget.min.js

widget.min.js

590 ms

bundle.e3b0a3eca8344d337272bdb317895260.js

bundle.e3b0a3eca8344d337272bdb317895260.js

450 ms

widget.min.js

widget.min.js

557 ms

dropdown.min.js

dropdown.min.js

459 ms

widget.min.js

widget.min.js

516 ms

bundle.b244f83f202a0d8a435fc31fd579db0a.js

bundle.b244f83f202a0d8a435fc31fd579db0a.js

501 ms

bundle.32dd910a990328f07de6cc8674681a5c.js

bundle.32dd910a990328f07de6cc8674681a5c.js

498 ms

widget.min.js

widget.min.js

539 ms

widget.min.js

widget.min.js

527 ms

variation.min.js

variation.min.js

486 ms

web-vitals.attribution.min.js

web-vitals.attribution.min.js

555 ms

index.min.js

index.min.js

506 ms

index.min.js

index.min.js

517 ms

ddc.jquery-ui.dialog.min.js

ddc.jquery-ui.dialog.min.js

596 ms

component.min.js

component.min.js

515 ms

DJ2RU-53A85-TRNP5-GC7S2-YSV7A

DJ2RU-53A85-TRNP5-GC7S2-YSV7A

150 ms

bebae4051af38f59b55f1a048a34ee30x.jpg

bebae4051af38f59b55f1a048a34ee30x.jpg

485 ms

blank.gif

blank.gif

89 ms

blank.gif

blank.gif

309 ms

blank.gif

blank.gif

257 ms

font.30b93b5e792bb054e3bbeafc88c30439.woff

font.30b93b5e792bb054e3bbeafc88c30439.woff

344 ms

842ddda19a69fa3875b2eee3de976872x.jpg

842ddda19a69fa3875b2eee3de976872x.jpg

421 ms

0ca1f5aa4333814013eda9fa85d53440x.jpg

0ca1f5aa4333814013eda9fa85d53440x.jpg

263 ms

18b2fca9ef783fc6c04462243dc16e4ax.jpg

18b2fca9ef783fc6c04462243dc16e4ax.jpg

282 ms

specials.jpg

specials.jpg

229 ms

cars-on-lot.jpg

cars-on-lot.jpg

334 ms

parts.jpg

parts.jpg

424 ms

analytics.js

analytics.js

75 ms

config.json

config.json

116 ms

js

js

76 ms

collect

collect

34 ms

bundle.a40e4a1a9fe3114712521a637d2772f1.js

bundle.a40e4a1a9fe3114712521a637d2772f1.js

44 ms

bundle.d99bdf9ab326d17171d64dca7e54e14e.js

bundle.d99bdf9ab326d17171d64dca7e54e14e.js

86 ms

Accessibility Review

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

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

critz.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

critz.com SEO score

99

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

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

critz.com

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