Tools & Wizards About Us
ppg.com screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

ppg.com

PPG: Innovating with Paints, Coatings, and Specialty Materials

Page Load Speed

2 sec in total

First Response

255 ms

Resources Loaded

966 ms

Page Rendered

738 ms

ppg.com screenshot

About Website

Visit ppg.com now to see the best up-to-date PPG content for Hong Kong and also check out these interesting facts you probably never knew about ppg.com

Discover how PPG’s global team of innovators drives sustainable solutions, enhances productivity, and celebrates 140 years of color leadership. Join us!

Visit ppg.com

Key Findings

We analyzed Ppg.com page load time and found that the first response time was 255 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

ppg.com performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value9.6 s

0/100

25%

SI (Speed Index)

Value3.7 s

86/100

10%

TBT (Total Blocking Time)

Value2,000 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.036

100/100

15%

TTI (Time to Interactive)

Value14.0 s

10/100

10%

Network Requests Diagram

www.ppg.com

255 ms

en-US

36 ms

gtm.js

131 ms

primer.min.css

17 ms

styles.min.css

38 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 34% of them (19 requests) were addressed to the original Ppg.com, 34% (19 requests) were made to Assets-us-01.kc-usercontent.com and 7% (4 requests) were made to Unpkg.com. The less responsive or slowest element that took the longest time to load (476 ms) relates to the external source Sdk.privacy-center.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 91.5 kB (5%)

Content Size

1.9 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-84%

Potential reduce by 55.7 kB

  • Original 66.2 kB
  • After minification 62.1 kB
  • After compression 10.5 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 55.7 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 0 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. PPG images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 20.7 kB

  • Original 136.9 kB
  • After minification 136.8 kB
  • After compression 116.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 20.7 kB or 15% of the original size.

CSS Optimization

-32%

Potential reduce by 15.1 kB

  • Original 46.6 kB
  • After minification 46.6 kB
  • After compression 31.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. Ppg.com needs all CSS files to be minified and compressed as it can save up to 15.1 kB or 32% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (45%)

Requests Now

51

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.ppg.com

www.ppg.com

255 ms

en-US

en-US

36 ms

gtm.js

gtm.js

131 ms

primer.min.css

primer.min.css

17 ms

styles.min.css

styles.min.css

38 ms

css2

css2

60 ms

jquery.min.js

jquery.min.js

47 ms

aos.css

aos.css

58 ms

blazor.server.js

blazor.server.js

53 ms

boot.js

boot.js

49 ms

site.js

site.js

48 ms

scriptLoader.js

scriptLoader.js

49 ms

algoliasearchLite.min.js

algoliasearchLite.min.js

44 ms

instantsearch.js@3.0.0

instantsearch.js@3.0.0

56 ms

aos.js

aos.js

76 ms

css2

css2

50 ms

aos.css

aos.css

24 ms

aos.js

aos.js

49 ms

pmr-icons.svg

pmr-icons.svg

60 ms

homepage-6-2200-optimized.jpg

homepage-6-2200-optimized.jpg

159 ms

ppg-logo.svg

ppg-logo.svg

94 ms

email.svg

email.svg

96 ms

play.svg

play.svg

92 ms

ppg-footer-logo.svg

ppg-footer-logo.svg

191 ms

linkedin.svg

linkedin.svg

96 ms

facebook.svg

facebook.svg

96 ms

instagram.svg

instagram.svg

109 ms

twitter.svg

twitter.svg

115 ms

threads.svg

threads.svg

114 ms

youtube.svg

youtube.svg

112 ms

PPGHomePageGraphics.png

PPGHomePageGraphics.png

99 ms

PPGHomePageGraphics_Glidden.png

PPGHomePageGraphics_Glidden.png

115 ms

Rectangle%202%20%282%29.png

Rectangle%202%20%282%29.png

105 ms

Sigma_PPGHomePageGraphics_PPG.png

Sigma_PPGHomePageGraphics_PPG.png

116 ms

Protect_and_Beautify_Video_1_320X200.jpg

Protect_and_Beautify_Video_1_320X200.jpg

106 ms

Rectangle%204156.png

Rectangle%204156.png

117 ms

Sustainability_Targets_Video_3_320X200.jpg

Sustainability_Targets_Video_3_320X200.jpg

120 ms

Rectangle%201.png

Rectangle%201.png

121 ms

download.jpg

download.jpg

122 ms

download.jpg

download.jpg

121 ms

download.jpg

download.jpg

186 ms

download.jpg

download.jpg

187 ms

download.jpg

download.jpg

207 ms

download.jpg

download.jpg

208 ms

download.jpg

download.jpg

188 ms

silica-ppg.jpg

silica-ppg.jpg

186 ms

PPG-Optical-Coatings.jpg

PPG-Optical-Coatings.jpg

208 ms

teslin-substrate.jpg

teslin-substrate.jpg

208 ms

loader.js

loader.js

476 ms

44332447.js

44332447.js

137 ms

font

font

39 ms

font

font

242 ms

banner.js

banner.js

64 ms

collectedforms.js

collectedforms.js

55 ms

44332447.js

44332447.js

60 ms

conversations-embed.js

conversations-embed.js

56 ms

Accessibility Review

ppg.com accessibility score

66

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes are not valid or misspelled

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

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

Missing source maps for large first-party JavaScript

SEO Factors

ppg.com SEO score

86

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ppg.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 Ppg.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

ppg.com

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