Tools & Wizards About Us
porscheorlandpark.com screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

porscheorlandpark.com

Porsche Chicago | New & Used Porsche Dealer | Porsche Orland Park

Page Load Speed

1.2 sec in total

First Response

55 ms

Resources Loaded

646 ms

Page Rendered

455 ms

porscheorlandpark.com screenshot

About Website

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

Receive the ultimate Porsche experience at the Porsche Orland Park dealership near Chicago, IL. Our philosophy is no pressure & hassle free shopping. Shop Now.

Visit porscheorlandpark.com

Key Findings

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

Performance Metrics

porscheorlandpark.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

55/100

10%

LCP (Largest Contentful Paint)

Value8.6 s

1/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value3,100 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.133

81/100

15%

TTI (Time to Interactive)

Value24.5 s

0/100

10%

Network Requests Diagram

www.porscheorlandpark.com

55 ms

dotagging.js

25 ms

dealerOnTrack.min.js

7 ms

js

215 ms

iframeInitializer.min.js

10 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 64% of them (45 requests) were addressed to the original Porscheorlandpark.com, 6% (4 requests) were made to Googletagmanager.com and 6% (4 requests) were made to Cdn.dlron.us. The less responsive or slowest element that took the longest time to load (372 ms) relates to the external source Cdn1.roadster.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 450.1 kB (18%)

Content Size

2.5 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-85%

Potential reduce by 393.1 kB

  • Original 464.8 kB
  • After minification 463.9 kB
  • After compression 71.8 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 393.1 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 5 B

  • Original 1.7 MB
  • After minification 1.7 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. Porsche Orland Park images are well optimized though.

JavaScript Optimization

-20%

Potential reduce by 57.0 kB

  • Original 289.9 kB
  • After minification 289.8 kB
  • After compression 232.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 57.0 kB or 20% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (50%)

Requests Now

62

After Optimization

31

  • AJAX
  • Images
  • JavaScript

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

Network Requests Diagram

www.porscheorlandpark.com

www.porscheorlandpark.com

55 ms

dotagging.js

dotagging.js

25 ms

dealerOnTrack.min.js

dealerOnTrack.min.js

7 ms

js

js

215 ms

iframeInitializer.min.js

iframeInitializer.min.js

10 ms

jquery-3.6.3.min.js

jquery-3.6.3.min.js

14 ms

ua-parser.min.js

ua-parser.min.js

19 ms

dealeron.js

dealeron.js

84 ms

dealeron.static.min.js

dealeron.static.min.js

85 ms

bootstrap.min.js

bootstrap.min.js

85 ms

userAgent-detection.min.js

userAgent-detection.min.js

84 ms

modernizr.min.js

modernizr.min.js

83 ms

jquery.validate.min.js

jquery.validate.min.js

198 ms

dealerOnLeadsBundle.js

dealerOnLeadsBundle.js

204 ms

locationSortInjection.min.js

locationSortInjection.min.js

199 ms

do_utility.min.js

do_utility.min.js

199 ms

formPhoneUtility.min.js

formPhoneUtility.min.js

198 ms

coreBundle.js

coreBundle.js

198 ms

navigation.min.js

navigation.min.js

203 ms

bannerManager.min.js

bannerManager.min.js

205 ms

lazyLoadHomepage.min.js

lazyLoadHomepage.min.js

203 ms

personalization.js

personalization.js

208 ms

analytics.min.js

analytics.min.js

195 ms

js

js

215 ms

fbevents.js

fbevents.js

283 ms

gtm.js

gtm.js

267 ms

gtm.js

gtm.js

255 ms

logo.png

logo.png

167 ms

porsche.svg

porsche.svg

161 ms

RIZ-POORL-GR-SP-2409-.jpg

RIZ-POORL-GR-SP-2409-.jpg

303 ms

RIZ-POORL-GR-SP-2409-3.jpg

RIZ-POORL-GR-SP-2409-3.jpg

304 ms

RIZ-POORL-GR-SP-2404-LeaseOpps-Revised.jpg

RIZ-POORL-GR-SP-2404-LeaseOpps-Revised.jpg

274 ms

Macan_1920x600_Option2.jpg

Macan_1920x600_Option2.jpg

276 ms

RIZ-POORL-GR-SP-2404-LeaseOpps5.jpg

RIZ-POORL-GR-SP-2404-LeaseOpps5.jpg

301 ms

1RIZ-POORL-GR-SP-2404-LeaseOpps3.jpg

1RIZ-POORL-GR-SP-2404-LeaseOpps3.jpg

332 ms

RIZ-POORL-GR-SP-2210-CPO.jpg

RIZ-POORL-GR-SP-2210-CPO.jpg

328 ms

bg-caret.png

bg-caret.png

301 ms

model-718.jpg

model-718.jpg

320 ms

model-911.jpg

model-911.jpg

309 ms

model-panamera.jpg

model-panamera.jpg

309 ms

model-taycan.jpg

model-taycan.jpg

310 ms

model-macan.jpg

model-macan.jpg

326 ms

model-cayenne.jpg

model-cayenne.jpg

321 ms

bg-gray.jpg

bg-gray.jpg

319 ms

quick-nav-1.jpg

quick-nav-1.jpg

321 ms

quick-nav-5.jpg

quick-nav-5.jpg

326 ms

quick-nav-2.jpg

quick-nav-2.jpg

324 ms

quick-nav-3.jpg

quick-nav-3.jpg

324 ms

bg-blueprint.png

bg-blueprint.png

328 ms

bg-gray-6.jpg

bg-gray-6.jpg

328 ms

quick-nav-14.jpg

quick-nav-14.jpg

328 ms

DealerOn_darkgray.png

DealerOn_darkgray.png

219 ms

PorscheNextWLa-Regular.woff

PorscheNextWLa-Regular.woff

158 ms

roadster_dealer_analytics

roadster_dealer_analytics

306 ms

roadster_frame_embed

roadster_frame_embed

372 ms

t.js

t.js

107 ms

partnermetrics.js

partnermetrics.js

148 ms

linkid.js

linkid.js

126 ms

PorscheNextWLa-Bold.woff

PorscheNextWLa-Bold.woff

113 ms

PorscheNextWLa-Thin.woff

PorscheNextWLa-Thin.woff

139 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

141 ms

snap-a2d8dZAhn5QyYc2fb.js

snap-a2d8dZAhn5QyYc2fb.js

154 ms

collect

collect

24 ms

collect

collect

44 ms

collect

collect

45 ms

recordMetricsData.action

recordMetricsData.action

56 ms

collect

collect

20 ms

tp2

tp2

12 ms

conversion_async.js

conversion_async.js

45 ms

carnow_plugin.js

carnow_plugin.js

55 ms

Accessibility Review

porscheorlandpark.com accessibility score

95

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

High

Heading elements are not in a sequentially-descending order

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

porscheorlandpark.com SEO score

92

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

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

porscheorlandpark.com

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