8.9 sec in total
463 ms
7.9 sec
594 ms
Click here to check amazing Corporate PPG content for Hong Kong. Otherwise, check out these important facts you probably never knew about corporate.ppg.com
At PPG, we work every day to develop and deliver the paints, coatings, and specialty materials that our customers have trusted for 140 years. Through dedication and creativity, we solve our customers’...
Visit corporate.ppg.comWe analyzed Corporate.ppg.com page load time and found that the first response time was 463 ms and then it took 8.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
corporate.ppg.com performance score
name
value
score
weighting
Value2.7 s
59/100
10%
Value5.3 s
22/100
25%
Value7.9 s
23/100
10%
Value150 ms
94/100
30%
Value0.545
13/100
15%
Value8.3 s
40/100
10%
463 ms
16 ms
6 ms
26 ms
7 ms
Our browser made a total of 163 requests to load all elements on the main page. We found that 18% of them (30 requests) were addressed to the original Corporate.ppg.com, 61% (100 requests) were made to Ppg-public.mc.wg1.kontiki.com and 2% (3 requests) were made to W.sharethis.com. The less responsive or slowest element that took the longest time to load (2.8 sec) relates to the external source Ppg-public.mc.wg1.kontiki.com.
Page size can be reduced by 1.9 MB (62%)
3.1 MB
1.2 MB
In fact, the total size of Corporate.ppg.com main page is 3.1 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. Javascripts take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 26.4 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 26.4 kB or 66% of the original size.
Potential reduce by 29.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. Corporate PPG images are well optimized though.
Potential reduce by 1.5 MB
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.5 MB or 73% of the original size.
Potential reduce by 353.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. Corporate.ppg.com needs all CSS files to be minified and compressed as it can save up to 353.3 kB or 81% of the original size.
Number of requests can be reduced by 130 (82%)
158
28
The browser has sent 158 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Corporate 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 83 to 1 for JavaScripts and from 33 to 1 for CSS and as a result speed up the page load time.
Home.aspx
463 ms
GetResource.ashx
16 ms
jquery-1.7.2.min.js
6 ms
GetResource.ashx
26 ms
buttons.js
7 ms
GetResource.ashx
19 ms
WebResource.axd
11 ms
GetResource.ashx
25 ms
GetResource.ashx
24 ms
ScriptResource.axd
18 ms
ScriptResource.axd
19 ms
PortalTemplate.aspx
92 ms
269357
14 ms
fp.js
183 ms
btn_search.aspx
150 ms
ppg_signature.aspx
149 ms
ppg_logo.aspx
150 ms
Download_on_the_App_Store.jpg.aspx
150 ms
google-play-store-175.png.aspx
150 ms
billboard_brands_logos.aspx
150 ms
billboard_fiberglass_icons
149 ms
AAAlogo.jpg.aspx
150 ms
trevor-in-lab-lowerresx.jpg.aspx
149 ms
MAW_MobileWebsiteHeader.png.aspx
152 ms
AGILONsilica_bottles.jpg.aspx
153 ms
Dream_Home_2016_SQ_color.png.aspx
152 ms
footer_logo.aspx
151 ms
player
840 ms
analytics.js
130 ms
info
157 ms
getAllAppDefault.esi
42 ms
bg_article_dot.aspx
56 ms
bg_search.aspx
55 ms
bg_nav.aspx
54 ms
icons_socialmedia_white.aspx
55 ms
billboard_renewable_wind_bw.aspx
87 ms
billboard_renewable_wind.aspx
75 ms
269357_0_0.aspx
85 ms
offsite_event.php
127 ms
umBeXf5EWiY
114 ms
collect
36 ms
getSegment.php
195 ms
checkOAuth.esi
30 ms
www-embed-player-vflQrT_sR.css
59 ms
www-embed-player.js
79 ms
base.js
159 ms
t.dhj
6 ms
t.dhj
18 ms
cm
22 ms
s-3271.xgi
140 ms
hbpix
170 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
78 ms
ad_status.js
77 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
127 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
136 ms
52 ms
31 ms
xrefid.xgi
27 ms
pixel
27 ms
2981
60 ms
reset.css
255 ms
default.css
243 ms
jquery.mmenu.css
403 ms
jquery.mmenu.positioning.css
439 ms
jquery.mmenu.themes.css
353 ms
menu.css
380 ms
nprogress.css
324 ms
footer.css
346 ms
jquery-1.10.2.min.js
798 ms
jquery-migrate-1.2.1.min.js
441 ms
jquery.base64.js
532 ms
jquery.cookie.js
471 ms
iso8601.min.js
482 ms
core.js
552 ms
jquery.i18n.properties-1.0.9.js
571 ms
kontiki.mc.config.data.js
630 ms
kontiki.settings.data.js
501 ms
jquery.dotdotdot.js
638 ms
kontiki.utils.js
899 ms
kontiki.browser.js
637 ms
common.menu.js
665 ms
kontiki.notification.js
723 ms
kontiki.extensions.js
727 ms
kontiki.mc.api.js
726 ms
kontiki.auth.js
852 ms
kontiki.template.settings.js
823 ms
kontiki.menu.js
814 ms
nprogress.js
813 ms
jquery.mmenu.js
821 ms
jquery-ui-1.10.0.css
1070 ms
jquery.countdown.css
907 ms
rateit.css
894 ms
jquery.tagit.css
908 ms
player.css
945 ms
tabby.css
974 ms
swfobject-2.2.js
887 ms
ZeroClipboard.js
811 ms
jquery.countdown.min.js
913 ms
jquery.rateit.js
783 ms
jquery-ui.min.js
1094 ms
jquery.tagit.js
772 ms
jwplayer.js
1020 ms
kontiki.agent.js
803 ms
kontiki.url.status.checker.js
766 ms
kontiki.jwplayer.reporting.js
871 ms
kontiki.jwplayer.utils.js
1007 ms
kontiki.player.js
910 ms
index.a8fc48294ca4cc10eb440189d9f22d7c.html
19 ms
buttons.ab966a004186897711de4a5ed256c924.css
11 ms
st.125da8bfe70ad3e00a35a6e4c65d8bc5.js
4 ms
player
165 ms
reset.css
88 ms
default.css
89 ms
jquery.mmenu.css
96 ms
jquery.mmenu.positioning.css
158 ms
jquery.mmenu.themes.css
174 ms
menu.css
175 ms
nprogress.css
189 ms
footer.css
236 ms
jquery-1.10.2.min.js
720 ms
jquery-migrate-1.2.1.min.js
260 ms
jquery.base64.js
261 ms
jquery.cookie.js
268 ms
iso8601.min.js
281 ms
core.js
315 ms
jquery.i18n.properties-1.0.9.js
346 ms
kontiki.settings.data.js
344 ms
jquery.dotdotdot.js
533 ms
kontiki.utils.js
468 ms
kontiki.browser.js
394 ms
common.menu.js
430 ms
kontiki.notification.js
431 ms
kontiki.extensions.js
474 ms
kontiki.auth.js
690 ms
kontiki.template.settings.js
517 ms
kontiki.menu.js
561 ms
nprogress.js
553 ms
jquery.mmenu.js
604 ms
jquery-ui-1.10.0.css
795 ms
jquery.countdown.css
631 ms
rateit.css
654 ms
jquery.tagit.css
690 ms
player.css
720 ms
tabby.css
750 ms
swfobject-2.2.js
774 ms
ZeroClipboard.js
778 ms
jquery.countdown.min.js
728 ms
jquery.rateit.js
717 ms
jquery-ui.min.js
1239 ms
jquery.tagit.js
866 ms
jwplayer.js
893 ms
kontiki.agent.js
709 ms
kontiki.url.status.checker.js
710 ms
kontiki.jwplayer.reporting.js
793 ms
kontiki.jwplayer.utils.js
809 ms
kontiki.player.js
785 ms
play_button.png
2760 ms
6b997aa5-7f7e-4d90-8a97-64a96c208fca;playback=true
147 ms
transparent.png
235 ms
t_0c95afd0-7836-40bf-a2d1-c5f670441ff4_IF3oLE.jpeg
622 ms
ui-bg_highlight-soft_100_eeeeee_1x100.png
152 ms
chevron-down.svg
240 ms
chevron-up.svg
330 ms
corporate.ppg.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<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
Image elements do not have [alt] attributes
Links do not have a discernible name
corporate.ppg.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
corporate.ppg.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Corporate.ppg.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 Corporate.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.
corporate.ppg.com
Open Graph description is not detected on the main page of Corporate PPG. 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: