Tools & Wizards About Us
porshaw.com screenshot

Report Summary

  • 67

    Performance

    Renders faster than
    79% of other websites

  • 51

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

porshaw.com

Porshaw - Porsche Parts, Repair & Service - Orange County, CA including Anaheim, Costa Mesa, Irvine, Newport Beach, Santa Ana

Page Load Speed

1.7 sec in total

First Response

214 ms

Resources Loaded

1.4 sec

Page Rendered

91 ms

porshaw.com screenshot

About Website

Click here to check amazing Porshaw content. Otherwise, check out these important facts you probably never knew about porshaw.com

Porshaw - Porsche parts, repairs and service for your Porsche 911, 930, 993, 996, 997, GT2, GT3, RS and RSR series vehicle(s). Anaheim, Costa Mesa, Newport Beach, Orange, Santa Ana

Visit porshaw.com

Key Findings

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

Performance Metrics

porshaw.com performance score

67

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

66/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value3.2 s

92/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.169

70/100

15%

TTI (Time to Interactive)

Value4.0 s

88/100

10%

Network Requests Diagram

porshaw.com

214 ms

style.css

91 ms

mootools.js

278 ms

slideshow.js

207 ms

slideshow.css

144 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 94% of them (74 requests) were addressed to the original Porshaw.com, 4% (3 requests) were made to Verify.authorize.net and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (479 ms) belongs to the original domain Porshaw.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 126.7 kB (29%)

Content Size

441.6 kB

After Optimization

315.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-75%

Potential reduce by 14.0 kB

  • Original 18.6 kB
  • After minification 16.5 kB
  • After compression 4.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 2.1 kB, which is 11% 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 14.0 kB or 75% of the original size.

Image Optimization

-4%

Potential reduce by 10.6 kB

  • Original 269.3 kB
  • After minification 258.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. Porshaw images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 88.1 kB

  • Original 137.5 kB
  • After minification 128.7 kB
  • After compression 49.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 88.1 kB or 64% of the original size.

CSS Optimization

-86%

Potential reduce by 13.9 kB

  • Original 16.2 kB
  • After minification 8.4 kB
  • After compression 2.3 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. Porshaw.com needs all CSS files to be minified and compressed as it can save up to 13.9 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 53 (69%)

Requests Now

77

After Optimization

24

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

porshaw.com

porshaw.com

214 ms

style.css

style.css

91 ms

mootools.js

mootools.js

278 ms

slideshow.js

slideshow.js

207 ms

slideshow.css

slideshow.css

144 ms

slideshow_defaultpage.css

slideshow_defaultpage.css

144 ms

slideshow_defaultfront.css

slideshow_defaultfront.css

145 ms

toplinks.js

toplinks.js

152 ms

pmen.js

pmen.js

226 ms

seal.js

seal.js

79 ms

seal.js

seal.js

80 ms

ga.js

ga.js

9 ms

__utm.gif

__utm.gif

15 ms

banner800x67.JPG

banner800x67.JPG

164 ms

topbar.gif

topbar.gif

129 ms

clearpixel.gif

clearpixel.gif

163 ms

littlecart1.gif

littlecart1.gif

130 ms

menutopcorn.gif

menutopcorn.gif

129 ms

porsche_parts_performance_service.png

porsche_parts_performance_service.png

161 ms

porshaw-shop.jpg

porshaw-shop.jpg

275 ms

rightline.gif

rightline.gif

192 ms

mahle_logo.gif

mahle_logo.gif

193 ms

bosch_logo-c.gif

bosch_logo-c.gif

231 ms

bilstein_logo.gif

bilstein_logo.gif

222 ms

sachs_logo.gif

sachs_logo.gif

223 ms

glyco_logo.jpg

glyco_logo.jpg

254 ms

toplinks_b1.gif

toplinks_b1.gif

245 ms

toplinks_b1_over.gif

toplinks_b1_over.gif

283 ms

toplinks_b1_on.gif

toplinks_b1_on.gif

283 ms

toplinks_b2.gif

toplinks_b2.gif

284 ms

toplinks_b2_over.gif

toplinks_b2_over.gif

305 ms

toplinks_b2_on.gif

toplinks_b2_on.gif

305 ms

toplinks_b3.gif

toplinks_b3.gif

326 ms

toplinks_b3_over.gif

toplinks_b3_over.gif

343 ms

toplinks_b3_on.gif

toplinks_b3_on.gif

346 ms

toplinks_b4.gif

toplinks_b4.gif

346 ms

toplinks_b4_over.gif

toplinks_b4_over.gif

367 ms

toplinks_b4_on.gif

toplinks_b4_on.gif

369 ms

toplinks_b5.gif

toplinks_b5.gif

384 ms

toplinks_b5_over.gif

toplinks_b5_over.gif

403 ms

toplinks_b5_on.gif

toplinks_b5_on.gif

405 ms

toplinks_b6.gif

toplinks_b6.gif

407 ms

toplinks_b6_over.gif

toplinks_b6_over.gif

427 ms

toplinks_b6_on.gif

toplinks_b6_on.gif

431 ms

pmen_b1.gif

pmen_b1.gif

455 ms

pmen_b1_over.gif

pmen_b1_over.gif

458 ms

pmen_b1_on.gif

pmen_b1_on.gif

458 ms

pmen_b2.gif

pmen_b2.gif

459 ms

pmen_b2_over.gif

pmen_b2_over.gif

479 ms

secure90x72.gif

secure90x72.gif

84 ms

pmen_b2_on.gif

pmen_b2_on.gif

377 ms

pmen_b3.gif

pmen_b3.gif

410 ms

pmen_b3_over.gif

pmen_b3_over.gif

413 ms

pmen_b3_on.gif

pmen_b3_on.gif

383 ms

pmen_b7.gif

pmen_b7.gif

392 ms

pmen_b7_over.gif

pmen_b7_over.gif

400 ms

pmen_b7_on.gif

pmen_b7_on.gif

376 ms

pmen_b8.gif

pmen_b8.gif

407 ms

pmen_b8_over.gif

pmen_b8_over.gif

382 ms

pmen_b8_on.gif

pmen_b8_on.gif

380 ms

loader-0.png

loader-0.png

66 ms

loader-1.png

loader-1.png

65 ms

loader-2.png

loader-2.png

64 ms

loader-3.png

loader-3.png

67 ms

loader-4.png

loader-4.png

65 ms

loader-5.png

loader-5.png

67 ms

loader-6.png

loader-6.png

124 ms

loader-7.png

loader-7.png

124 ms

loader-8.png

loader-8.png

124 ms

loader-9.png

loader-9.png

126 ms

loader-10.png

loader-10.png

126 ms

loader-11.png

loader-11.png

128 ms

controller.png

controller.png

184 ms

controller-first.gif

controller-first.gif

183 ms

controller-prev.gif

controller-prev.gif

184 ms

controller-pause.gif

controller-pause.gif

185 ms

controller-next.gif

controller-next.gif

187 ms

controller-last.gif

controller-last.gif

188 ms

engines500.jpg

engines500.jpg

176 ms

Accessibility Review

porshaw.com accessibility score

51

Accessibility Issues

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

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

porshaw.com best practices score

58

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

porshaw.com SEO score

62

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Porshaw.com 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 Porshaw.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

porshaw.com

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