7.9 sec in total
3.1 sec
3.9 sec
928 ms
Click here to check amazing Us Pg content for United States. Otherwise, check out these important facts you probably never knew about us.pg.com
Our goal is to use every opportunity we have—no matter how small—to set change in motion. To be a force for good and a force for growth. For you, for the world, and for every generation to come.
Visit us.pg.comWe analyzed Us.pg.com page load time and found that the first response time was 3.1 sec and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
us.pg.com performance score
name
value
score
weighting
Value17.2 s
0/100
10%
Value27.0 s
0/100
25%
Value21.1 s
0/100
10%
Value10,260 ms
0/100
30%
Value0.001
100/100
15%
Value39.9 s
0/100
10%
3078 ms
71 ms
75 ms
32 ms
24 ms
Our browser made a total of 47 requests to load all elements on the main page. We found that 85% of them (40 requests) were addressed to the original Us.pg.com, 11% (5 requests) were made to Fast.fonts.net and 2% (1 request) were made to S.btstatic.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Us.pg.com.
Page size can be reduced by 555.1 kB (42%)
1.3 MB
776.0 kB
In fact, the total size of Us.pg.com main page is 1.3 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. 55% of websites need less resources to load. Images take 698.8 kB which makes up the majority of the site volume.
Potential reduce by 123.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. This page needs HTML code to be minified as it can gain 48.5 kB, which is 36% 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 123.5 kB or 91% of the original size.
Potential reduce by 2.7 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. Us Pg images are well optimized though.
Potential reduce by 34.5 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 34.5 kB or 69% of the original size.
Potential reduce by 394.4 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. Us.pg.com needs all CSS files to be minified and compressed as it can save up to 394.4 kB or 88% of the original size.
Number of requests can be reduced by 18 (44%)
41
23
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Us Pg. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and as a result speed up the page load time.
us.pg.com
3078 ms
ca9d29d5-c26c-4c7b-b461-8ce3c22e6218.css
71 ms
main.css
75 ms
modernizr
32 ms
jquery
24 ms
jquerylibs
65 ms
BootstrapUI.js
12 ms
jquery.columnizer.min.js
23 ms
jquery.cookie.js
24 ms
bootstrap-modal.js
35 ms
PGCORPen-US
36 ms
tag.js
41 ms
selected_country_arrows.png
123 ms
headerbg.png
73 ms
logo%20png.png
71 ms
home_herofullwidth_d%20jpg.jpg
79 ms
home_bubble.png
69 ms
pg_home_featurepromo_offers%20jpg.png
104 ms
arrow-link-highlight.png
68 ms
home_careers_d%20jpg.jpg
70 ms
arrow_circle%20png.png
73 ms
home_investors_d%20jpg.jpg
71 ms
home_brands_bg_d%20jpg.jpg
70 ms
home_brands_d%20png.png
73 ms
home_whoweare_ourvalues_d%20png.jpg
71 ms
pg_home_whoweare_heritage_mosaic%20jpg.jpg
98 ms
pg_home_sustainability_environmental_mosaic%20jpg.jpg
75 ms
home_sustainability_social_d%20png.jpg
73 ms
news-links.png
72 ms
pg_home_externalfeed%20jpg.jpg
84 ms
footer_bg%20jpg.jpg
93 ms
brand-icon.png
94 ms
Facebook%20png.png
100 ms
Twitter%20png.png
94 ms
youtube%20png.png
95 ms
instagram%20png.png
95 ms
linkedin%20png.png
97 ms
bbb_logo%20png.png
229 ms
touching-lives%20png.png
227 ms
logo.png
226 ms
f5000873-22b4-4c18-8586-7ee65a4a320c.woff
144 ms
35e93eea-6c4f-4f52-ae37-a51202e3855e.woff
143 ms
219dbe94-8d11-46eb-9311-7d6b7c093991.woff
143 ms
90958113-caad-4449-b52a-c94dc1af18c8.woff
143 ms
glyphicons-halflings-regular.woff
140 ms
tag
109 ms
external-link-caret.png
19 ms
us.pg.com accessibility score
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
[aria-hidden="true"] elements contain focusable descendents
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
Form elements do not have associated labels
us.pg.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
us.pg.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Us.pg.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 Us.pg.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.
us.pg.com
Open Graph data is detected on the main page of Us Pg. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: