C — https://pg.com | BeaverCheck Audit

Site Health

Score: 79 / 100

Based on 8 categories, 0 sections

Fast site — your users get a smooth experience.

Good foundation, but a few gaps could be exploited.

Several issues make your site difficult for assistive technology users.

Solid SEO basics — a few optimizations could boost rankings.

Good server performance with room for optimization.

Mostly compliant — a few items need attention.

Rich content metadata — your pages look great everywhere.

Lean and efficient — low environmental impact per visit.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

Contentful · 80 peers

You 79

Avg 73

+6 above average

0 50 100

Better than 91% of Contentful sites See full Contentful benchmark →

Azure DNS · 83 peers

You 79

Avg 72

+7 above average

0 50 100

Better than 96% of Azure DNS sites See full Azure DNS benchmark →

Top Priorities (5)

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers

HSTS header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy

Soft 404: server returns HTTP 200 for non-existent pages

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › 404 Error Page

64 third-party resources (100% of weight)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Inventory

View fix priority matrix

Fix Priority Matrix

5 findings

Impact

Quick Wins

High impact, low effort — start here.

Strategic

High impact, requires investment.

Easy Improvements

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fpg.com)](https://beavercheck.com/results/af73abac-b5df-4cad-8a63-4ae26f5d6052)

HTML

<a href="https://beavercheck.com/results/af73abac-b5df-4cad-8a63-4ae26f5d6052"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fpg.com" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fpg.com

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 4.8s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Addressing the critical issues below would have the most immediate impact on your user trust.

3 security gaps detected — browsers may warn visitors about your site.

1 accessibility issue excludes users who rely on assistive technology.

Your LCP is 4.8s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.

Could reach Estimate based on resolving critical issues

Conversion Barriers

2 critical 2 warning

4 barrier(s) likely increasing bounce by ~23%.

Speed (1)

Page takes 4.8s to load

+12% bounce

Users abandon at ~3s — you're 2.3s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

Trust (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Navigation (1)

4 broken link(s) on the page

+5% bounce

Clicks land on 404s — trust drops and the session often ends

Fix: Fix or remove the broken destinations surfaced on the Content tab

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

$500 investment → $3,589/month returns + USD 157,500 risk avoided

Payback period: < 1 month First-year ROI: +8514%

Investment

$500

5h · 5 findings

Monthly returns

$3,589 /mo

~$43,072 / year

Conversions recovered $3,589
Bandwidth savings $0.19

Regulatory risk avoided

USD 157,500

if kept compliant

ADA Title III USD 150,000
CCPA/CPRA USD 7,500

Payback period

0 12mo 24mo

$150 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

$500

5.0 developer hours at $100/hr

Based on United States rates ($100/hr)

Quick wins

$150 3 fixes in ~90 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions

Custom rate

$ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

$13,125 / month at risk

~$157,502 / year if left unfixed

Compliance Risk

$157,500

ADA Title IIICCPA/CPRA

No privacy policy link detected
CCPA/CPRA: USD 2,500 – USD 7,500
Trackers detected but no cookie policy found
CCPA/CPRA: USD 2,500 – USD 7,500
Trackers detected but no privacy policy found
CCPA/CPRA: USD 2,500 – USD 7,500

+2 more

Bandwidth Waste

$0.19 /mo

2318.9 MB/mo × 0.080 USD/GB

Optimize transfer: save ~232 KB per page load
Saves $0.19/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Monthly visitors

Unique monthly visitors from your analytics

Conversion rate (%)

Purchases, signups, or key actions

Avg. order value

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue

Current bounce (est.)

After fixes (est.)

Estimated bounce reduction

Fix 4 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

Best Practices

SEO

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

3.49 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

4.77 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

170 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.032

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

4.46 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

6.02 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:57.167 source:map[type:text value:[unattributed]]]]

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

value: no origins were preconnected

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
Blue circle with P&G logo and a black badge honoring "America's Most Innovative… `a.blog-item > div.blog-item__image-container > div.image > img.image__file`	/oggad6svuzkv/7p23uPFqJh9ZXx1Sn4rPY6/e277c58cddcbe9d8d85f...	122.0 KiB	96.0 KiB
2026 Where You Work Matters Platinum Employer badge `div.hp-header__container > div.image > picture.image__set > img.image__file`	/oggad6svuzkv/uXNEr2qCMu8ws7qQ2Ppcr/521d668ba39d547dacdac...	16.3 KiB	12.6 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 2.3 s

URL	Time Spent
pg.com/	1.0 s
www.pg.com/	1.2 s
us.pg.com/	0.0 ms

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 150 ms 21.9 KiB

URL	Transfer Size	Est Savings
us.pg.com/css/WKCCCVRdYqHv.css	26.2 KiB	21.9 KiB

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Other	1.1 s
Script Evaluation	830 ms
Style & Layout	610 ms
Rendering	287 ms
Parse HTML & CSS	172 ms
Script Parsing & Compilation	71 ms
Garbage Collection	11 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not actionable

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Estimated savings: 0.0 ms 237.8 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtm.js?id=GTM-N6XWT7TZ	239.4 KiB	78.9 KiB
www.googletagmanager.com/gtm.js?id=GTM-P28RLW7	135.1 KiB	77.5 KiB
www.googletagmanager.com/gtag/destination?id=G-ERH9Q0H5WB&cx=c&gtm=4e64k0	135.8 KiB	60.8 KiB
us.pg.com/_next/static/chunks/0ut-es-m5f4j0.js	60.8 KiB	20.7 KiB

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Use efficient cache lifetimes

●Layout shift culprits

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 755 KiB

●User Timing marks and measures 7 user timings

●JavaScript execution time 0.8 s

●Avoid long main-thread tasks 6 long tasks found

●Avoid non-composited animations 115 animated elements found

●Image elements have explicit `width` and `height`

●Network Requests

●Network Round Trip Times 100 ms

●Server Backend Latencies 480 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 360 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Contact Careers Partners & Investors Investors Partner with us Suppliers Our Co… `li#global-navigation > ul.navigation__group__items > li#global-navigation-footer > ul.navigation__group__items`

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

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
4/22/2026 Inspiring More Sustainable Habits Through Thoughtful Design and Inno… `div.slick-track > div.slick-slide > div > a.blog-item`
See our efforts `div.hp-msg > div.hp-msg__wrapper > div.hp-msg__content > a.external-link`

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●ARIA attributes are used as specified for the element's role

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links have a discernible name

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Aspect Ratio (Displayed)	Aspect Ratio (Actual)
Placeholder `div.page-container > main#page-content > div > img.lcp`		392 x 803 (0.49)	640 x 360 (1.78)

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Displayed size	Actual size	Expected size
Placeholder `div.page-container > main#page-content > div > img.lcp`		392 x 803	640 x 360	588 x 1205
2026 Where You Work Matters Platinum Employer badge `div.hp-header__container > div.image > picture.image__set > img.image__file`	/oggad6svuzkv/uXNEr2qCMu8ws7qQ2Ppcr/521d668ba39d547dacdac...	150 x 150	150 x 150	225 x 225

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
us.pg.com/_next/static/chunks/0w_5tmlm5w8y8.js	Connecting to 'https://privacytermsprod.pgmodernweb.com/privacy/privacy_and_terms_v2.json' violates the following Content Security Policy directive: "connect-src 'self' https://www.google.com https://geolocation.onetrust.com https://feeds.businesswire.com https://csapi-nonprod.pg.com https://csapi.pg.com https://downloads.ctfassets.net https://cdn.segment.com https://privacytermsprod.azureedge.net https://assets.ctfassets.net/ https://cdn.contentful.com https://mw-ar-recom-prod.pgapi.io/ https://staging-api.fr.pg.com/ https://gpdb-staging.name-coach.com/api/public/v1/pronunciations/phonetics https://gpdb.name-coach.com/api/public/v1/pronunciations/phonetics https://prompts.maze.co https://pagestates-tracking.crazyegg.com https://assets-tracking.crazyegg.com https://tracking.crazyegg.com https://api.fr.pg.com https://pg-poc-regulatory-app-test.azurewebsites.net https://s.swiftypecdn.com https://maps.googleapis.com https://script.crazyegg.com https://consent-api.onetrust.com https://api.segment.io/ https://match.adsrvr.org/ https://lj18wdvpyu-3.algolianet.com/ https://lj18wdvpyu-2.algolianet.com/ https://lj18wdvpyu-1.algolianet.com/ https://lj18wdvpyu-dsn.algolia.net/ https://www.google-analytics.com/ https://region1.google-analytics.com https://cdn.cookielaw.org .rudderstack.com cdn.rudderlabs.com .doubleclick.net https://stats.g.doubleclick.net". The action has been blocked.
us.pg.com/_next/static/chunks/0w_5tmlm5w8y8.js	Connecting to 'https://privacytermsprod.pgmodernweb.com/privacy/privacy_and_terms_v2.json' violates the following Content Security Policy directive: "connect-src 'self' https://www.google.com https://geolocation.onetrust.com https://feeds.businesswire.com https://csapi-nonprod.pg.com https://csapi.pg.com https://downloads.ctfassets.net https://cdn.segment.com https://privacytermsprod.azureedge.net https://assets.ctfassets.net/ https://cdn.contentful.com https://mw-ar-recom-prod.pgapi.io/ https://staging-api.fr.pg.com/ https://gpdb-staging.name-coach.com/api/public/v1/pronunciations/phonetics https://gpdb.name-coach.com/api/public/v1/pronunciations/phonetics https://prompts.maze.co https://pagestates-tracking.crazyegg.com https://assets-tracking.crazyegg.com https://tracking.crazyegg.com https://api.fr.pg.com https://pg-poc-regulatory-app-test.azurewebsites.net https://s.swiftypecdn.com https://maps.googleapis.com https://script.crazyegg.com https://consent-api.onetrust.com https://api.segment.io/ https://match.adsrvr.org/ https://lj18wdvpyu-3.algolianet.com/ https://lj18wdvpyu-2.algolianet.com/ https://lj18wdvpyu-1.algolianet.com/ https://lj18wdvpyu-dsn.algolia.net/ https://www.google-analytics.com/ https://region1.google-analytics.com https://cdn.cookielaw.org .rudderstack.com cdn.rudderlabs.com .doubleclick.net https://stats.g.doubleclick.net". The action has been blocked.
us.pg.com/_next/static/chunks/0w_5tmlm5w8y8.js	Error: TypeError: Failed to fetch at p (https://us.pg.com/_next/static/chunks/0w_5tmlm5w8y8.js:1:15013) at v (https://us.pg.com/_next/static/chunks/0w_5tmlm5w8y8.js:1:15255) at a (https://us.pg.com/_next/static/chunks/0w_5tmlm5w8y8.js:1:17418) at https://us.pg.com/_next/static/chunks/0w_5tmlm5w8y8.js:1:17678 at oJ (https://us.pg.com/_next/static/chunks/0ut-es-m5f4j0.js:1:94508) at uk (https://us.pg.com/_next/static/chunks/0ut-es-m5f4j0.js:1:110396) at uw (https://us.pg.com/_next/static/chunks/0ut-es-m5f4j0.js:1:110280) at uk (https://us.pg.com/_next/static/chunks/0ut-es-m5f4j0.js:1:110441) at uw (https://us.pg.com/_next/static/chunks/0ut-es-m5f4j0.js:1:110280) at uk (https://us.pg.com/_next/static/chunks/0ut-es-m5f4j0.js:1:110376)
us.pg.com/_next/static/chunks/0w_5tmlm5w8y8.js	Error: TypeError: Failed to fetch at p (https://us.pg.com/_next/static/chunks/0w_5tmlm5w8y8.js:1:15013) at v (https://us.pg.com/_next/static/chunks/0w_5tmlm5w8y8.js:1:15255) at a (https://us.pg.com/_next/static/chunks/0w_5tmlm5w8y8.js:1:17418) at https://us.pg.com/_next/static/chunks/0w_5tmlm5w8y8.js:1:17678 at oJ (https://us.pg.com/_next/static/chunks/0ut-es-m5f4j0.js:1:94508) at uk (https://us.pg.com/_next/static/chunks/0ut-es-m5f4j0.js:1:110396) at uw (https://us.pg.com/_next/static/chunks/0ut-es-m5f4j0.js:1:110280) at uk (https://us.pg.com/_next/static/chunks/0ut-es-m5f4j0.js:1:110441) at uw (https://us.pg.com/_next/static/chunks/0ut-es-m5f4j0.js:1:110280) at uk (https://us.pg.com/_next/static/chunks/0ut-es-m5f4j0.js:1:110376)
us.pg.com/_next/static/chunks/0w_5tmlm5w8y8.js	`Fetch API cannot load https://privacytermsprod.pgmodernweb.com/privacy/privacy_and_terms_v2.json. Refused to connect because it violates the document's Content Security Policy.`
us.pg.com/_next/static/chunks/0w_5tmlm5w8y8.js	`Fetch API cannot load https://privacytermsprod.pgmodernweb.com/privacy/privacy_and_terms_v2.json. Refused to connect because it violates the document's Content Security Policy.`
	TypeError: Cannot set properties of undefined (setting 'dimension16') at <anonymous>:1:34 at f.ba (https://www.googletagmanager.com/gtm.js?id=GTM-P28RLW7:180:229) at f.ka (https://www.googletagmanager.com/gtm.js?id=GTM-P28RLW7:179:427) at f.Y (https://www.googletagmanager.com/gtm.js?id=GTM-P28RLW7:177:407) at f.F (https://www.googletagmanager.com/gtm.js?id=GTM-P28RLW7:175:445) at f.write (https://www.googletagmanager.com/gtm.js?id=GTM-P28RLW7:175:70) at f (https://www.googletagmanager.com/gtm.js?id=GTM-P28RLW7:182:215) at e (https://www.googletagmanager.com/gtm.js?id=GTM-P28RLW7:181:279) at q.streams (https://www.googletagmanager.com/gtm.js?id=GTM-P28RLW7:183:30) at d (https://www.googletagmanager.com/gtm.js?id=GTM-P28RLW7:883:303)
	TypeError: Cannot set properties of undefined (setting 'dimension19') at <anonymous>:1:34 at f.ba (https://www.googletagmanager.com/gtm.js?id=GTM-P28RLW7:180:229) at f.ka (https://www.googletagmanager.com/gtm.js?id=GTM-P28RLW7:179:427) at f.Y (https://www.googletagmanager.com/gtm.js?id=GTM-P28RLW7:177:407) at f.F (https://www.googletagmanager.com/gtm.js?id=GTM-P28RLW7:175:445) at f.write (https://www.googletagmanager.com/gtm.js?id=GTM-P28RLW7:175:70) at f (https://www.googletagmanager.com/gtm.js?id=GTM-P28RLW7:182:215) at e (https://www.googletagmanager.com/gtm.js?id=GTM-P28RLW7:181:279) at q.streams (https://www.googletagmanager.com/gtm.js?id=GTM-P28RLW7:183:30) at d (https://www.googletagmanager.com/gtm.js?id=GTM-P28RLW7:883:303)
www.googletagmanager.com/gtm.js?id=GTM-P28RLW7 line 172, col 503	`Uncaught [object Object]`
www.googletagmanager.com/gtm.js?id=GTM-P28RLW7 line 172, col 503	`Uncaught [object Object]`

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Content security policy

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Page has the HTML doctype

●Properly defines charset

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destination	Link Text
us.pg.com/blogs/pg-awards-and-recognitions/	Read More

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

Crawling and Indexing

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Line #	Content	Error
4	`Disallow: https://origprod-cus-us.pg.com/health-probe/`	`Pattern should either be empty, start with "/" or "*"`
5	`Disallow: https://origprod-eus2-us.pg.com/health-probe/`	`Pattern should either be empty, start with "/" or "*"`
6	`Disallow: https://us.pg.com/health-probe/`	`Pattern should either be empty, start with "/" or "*"`

To appear in search results, crawlers need access to your app.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links are crawlable

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

100

Accessibility

Best Practices

SEO

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.64 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

2.06 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

1 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

4.45 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

2.11 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
Blue circle with P&G logo and a black badge honoring "America's Most Innovative… `a.blog-item > div.blog-item__image-container > div.image > img.image__file`	/oggad6svuzkv/7p23uPFqJh9ZXx1Sn4rPY6/e277c58cddcbe9d8d85f...	122.0 KiB	108.7 KiB
div.hp-header__image > div.image > picture.image__set > img.image__file `div.hp-header__image > div.image > picture.image__set > img.image__file`	/oggad6svuzkv/6n6TXJCqYs5ID8JQ6f3hNh/1aea28122c65f51ed928...	187.9 KiB	90.3 KiB
div.hp-header__image > div.image > picture.image__set > img.image__file `div.hp-header__image > div.image > picture.image__set > img.image__file`	/oggad6svuzkv/1qWaKI94Q2uelcBWImnlAB/49d835a31220b79ffa26...	114.9 KiB	55.2 KiB
div.hp-header__image > div.image > picture.image__set > img.image__file `div.hp-header__image > div.image > picture.image__set > img.image__file`	/oggad6svuzkv/3vshmiZPCvCJnHycOnvwyl/3d3c3b195c1ce46ac868...	98.1 KiB	47.1 KiB
div.hp-header__image > div.image > picture.image__set > img.image__file `div.hp-header__image > div.image > picture.image__set > img.image__file`	/oggad6svuzkv/iWOtUUreZAMiN6daJ2JMn/974515dfda27058562397...	71.2 KiB	34.2 KiB
2026 Where You Work Matters Platinum Employer badge `div.hp-header__container > div.image > picture.image__set > img.image__file`	/oggad6svuzkv/2CfEkcZXpQMywhZAqOOfGy/089b54a9f201722d09d1...	30.5 KiB	20.3 KiB
A man with short brown hair wears a grey t-shirt and black pants. He is standin… `a.blog-item > div.blog-item__image-container > div.image > img.image__file`	/oggad6svuzkv/1hjTPHfLoqsyLTxHbE1iLw/78a55c41f9275f821f78...	28.9 KiB	15.6 KiB
A man with long hair and a blue shirt removed laundry from the dryer as a smili… `a.blog-item > div.blog-item__image-container > div.image > img.image__file`	/oggad6svuzkv/6QTtd6YftUnRym3ahSxDG3/de8f687937a9a64b776e...	26.9 KiB	13.6 KiB
A man in a light blue shirt and black suit jacket. He is wearing a microphone a… `a.blog-item > div.blog-item__image-container > div.image > img.image__file`	/oggad6svuzkv/20BkCb2AxAWQJK2JEDaRkx/e0729e410dd4242d9099...	15.6 KiB	7.6 KiB

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]

items: [map[duration:3862.165 label:Time to first byte subpart:timeToFirstByte] map[duration:950.144 label:Element render delay subpart:elementRenderDelay]]

lhId: page-9-IMG

nodeLabel: Placeholder

path: 1,HTML,1,BODY,1,DIV,0,DIV,1,MAIN,0,DIV,0,IMG

selector: div.page-container > main#page-content > div > img.lcp

snippet: <img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAoAAAAFoCAQAAABtO4LaAAADB3pU…" alt="Placeholder" width="100%" height="100%" class="lcp" style="position:absolute;z-index:-1;padding:10px;max-width:100%;left:0;top:0">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

title: Preconnected origins

value: no origins were preconnected

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 40 ms 20.3 KiB

URL	Transfer Size	Est Savings
us.pg.com/css/WKCCCVRdYqHv.css	25.9 KiB	20.3 KiB

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not actionable

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

Source: Google web.dev / Lighthouse

Estimated savings: 0.0 ms 20.6 KiB

URL	Transfer Size	Est Savings
us.pg.com/_next/static/chunks/0ut-es-m5f4j0.js	60.4 KiB	20.6 KiB

More information about the performance of your application. These numbers don't directly affect the Performance score.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.3 s

URL	Time Spent
pg.com/	438 ms
www.pg.com/	896 ms
us.pg.com/	0.0 ms

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 3.3 s

URL	Time Spent
us.pg.com/	3.4 s

●Time to Interactive 2.1 s

●Use efficient cache lifetimes

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Max Potential First Input Delay 50 ms

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 1,137 KiB

●User Timing marks and measures 7 user timings

●JavaScript execution time 0.1 s

●Minimizes main-thread work 0.6 s

●Avoid long main-thread tasks 1 long task found

●Avoid non-composited animations 5 animated elements found

●Image elements have explicit `width` and `height`

●Network Requests

●Network Round Trip Times 100 ms

●Server Backend Latencies 700 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

100

Accessibility

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
USA `li#global-navigation > ul.navigation__group__items > li.navigation__item > a#change-location-header`
See our efforts `div.hp-msg > div.hp-msg__wrapper > div.hp-msg__content > a.external-link`

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●ARIA attributes are used as specified for the element's role

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Aspect Ratio (Displayed)	Aspect Ratio (Actual)
Placeholder `div.page-container > main#page-content > div > img.lcp`		1330 x 920 (1.45)	640 x 360 (1.78)

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Displayed size	Actual size	Expected size
Placeholder `div.page-container > main#page-content > div > img.lcp`		1330 x 920	640 x 360	1330 x 920

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
us.pg.com/_next/static/chunks/0w_5tmlm5w8y8.js	Connecting to 'https://privacytermsprod.pgmodernweb.com/privacy/privacy_and_terms_v2.json' violates the following Content Security Policy directive: "connect-src 'self' https://www.google.com https://geolocation.onetrust.com https://feeds.businesswire.com https://csapi-nonprod.pg.com https://csapi.pg.com https://downloads.ctfassets.net https://cdn.segment.com https://privacytermsprod.azureedge.net https://assets.ctfassets.net/ https://cdn.contentful.com https://mw-ar-recom-prod.pgapi.io/ https://staging-api.fr.pg.com/ https://gpdb-staging.name-coach.com/api/public/v1/pronunciations/phonetics https://gpdb.name-coach.com/api/public/v1/pronunciations/phonetics https://prompts.maze.co https://pagestates-tracking.crazyegg.com https://assets-tracking.crazyegg.com https://tracking.crazyegg.com https://api.fr.pg.com https://pg-poc-regulatory-app-test.azurewebsites.net https://s.swiftypecdn.com https://maps.googleapis.com https://script.crazyegg.com https://consent-api.onetrust.com https://api.segment.io/ https://match.adsrvr.org/ https://lj18wdvpyu-3.algolianet.com/ https://lj18wdvpyu-2.algolianet.com/ https://lj18wdvpyu-1.algolianet.com/ https://lj18wdvpyu-dsn.algolia.net/ https://www.google-analytics.com/ https://region1.google-analytics.com https://cdn.cookielaw.org .rudderstack.com cdn.rudderlabs.com .doubleclick.net https://stats.g.doubleclick.net". The action has been blocked.
us.pg.com/_next/static/chunks/0w_5tmlm5w8y8.js	Connecting to 'https://privacytermsprod.pgmodernweb.com/privacy/privacy_and_terms_v2.json' violates the following Content Security Policy directive: "connect-src 'self' https://www.google.com https://geolocation.onetrust.com https://feeds.businesswire.com https://csapi-nonprod.pg.com https://csapi.pg.com https://downloads.ctfassets.net https://cdn.segment.com https://privacytermsprod.azureedge.net https://assets.ctfassets.net/ https://cdn.contentful.com https://mw-ar-recom-prod.pgapi.io/ https://staging-api.fr.pg.com/ https://gpdb-staging.name-coach.com/api/public/v1/pronunciations/phonetics https://gpdb.name-coach.com/api/public/v1/pronunciations/phonetics https://prompts.maze.co https://pagestates-tracking.crazyegg.com https://assets-tracking.crazyegg.com https://tracking.crazyegg.com https://api.fr.pg.com https://pg-poc-regulatory-app-test.azurewebsites.net https://s.swiftypecdn.com https://maps.googleapis.com https://script.crazyegg.com https://consent-api.onetrust.com https://api.segment.io/ https://match.adsrvr.org/ https://lj18wdvpyu-3.algolianet.com/ https://lj18wdvpyu-2.algolianet.com/ https://lj18wdvpyu-1.algolianet.com/ https://lj18wdvpyu-dsn.algolia.net/ https://www.google-analytics.com/ https://region1.google-analytics.com https://cdn.cookielaw.org .rudderstack.com cdn.rudderlabs.com .doubleclick.net https://stats.g.doubleclick.net". The action has been blocked.
us.pg.com/_next/static/chunks/0w_5tmlm5w8y8.js	Error: TypeError: Failed to fetch at p (https://us.pg.com/_next/static/chunks/0w_5tmlm5w8y8.js:1:15013) at v (https://us.pg.com/_next/static/chunks/0w_5tmlm5w8y8.js:1:15255) at a (https://us.pg.com/_next/static/chunks/0w_5tmlm5w8y8.js:1:17418) at https://us.pg.com/_next/static/chunks/0w_5tmlm5w8y8.js:1:17678 at oJ (https://us.pg.com/_next/static/chunks/0ut-es-m5f4j0.js:1:94508) at uk (https://us.pg.com/_next/static/chunks/0ut-es-m5f4j0.js:1:110396) at uw (https://us.pg.com/_next/static/chunks/0ut-es-m5f4j0.js:1:110280) at uk (https://us.pg.com/_next/static/chunks/0ut-es-m5f4j0.js:1:110441) at uw (https://us.pg.com/_next/static/chunks/0ut-es-m5f4j0.js:1:110280) at uk (https://us.pg.com/_next/static/chunks/0ut-es-m5f4j0.js:1:110376)
us.pg.com/_next/static/chunks/0w_5tmlm5w8y8.js	Error: TypeError: Failed to fetch at p (https://us.pg.com/_next/static/chunks/0w_5tmlm5w8y8.js:1:15013) at v (https://us.pg.com/_next/static/chunks/0w_5tmlm5w8y8.js:1:15255) at a (https://us.pg.com/_next/static/chunks/0w_5tmlm5w8y8.js:1:17418) at https://us.pg.com/_next/static/chunks/0w_5tmlm5w8y8.js:1:17678 at oJ (https://us.pg.com/_next/static/chunks/0ut-es-m5f4j0.js:1:94508) at uk (https://us.pg.com/_next/static/chunks/0ut-es-m5f4j0.js:1:110396) at uw (https://us.pg.com/_next/static/chunks/0ut-es-m5f4j0.js:1:110280) at uk (https://us.pg.com/_next/static/chunks/0ut-es-m5f4j0.js:1:110441) at uw (https://us.pg.com/_next/static/chunks/0ut-es-m5f4j0.js:1:110280) at uk (https://us.pg.com/_next/static/chunks/0ut-es-m5f4j0.js:1:110376)
us.pg.com/_next/static/chunks/0w_5tmlm5w8y8.js	`Fetch API cannot load https://privacytermsprod.pgmodernweb.com/privacy/privacy_and_terms_v2.json. Refused to connect because it violates the document's Content Security Policy.`
us.pg.com/_next/static/chunks/0w_5tmlm5w8y8.js	`Fetch API cannot load https://privacytermsprod.pgmodernweb.com/privacy/privacy_and_terms_v2.json. Refused to connect because it violates the document's Content Security Policy.`

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Content security policy

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Page has the HTML doctype

●Properly defines charset

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

SEO

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destination	Link Text
us.pg.com/blogs/pg-awards-and-recognitions/	Read More

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

Crawling and Indexing

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Line #	Content	Error
4	`Disallow: https://origprod-cus-us.pg.com/health-probe/`	`Pattern should either be empty, start with "/" or "*"`
5	`Disallow: https://origprod-eus2-us.pg.com/health-probe/`	`Pattern should either be empty, start with "/" or "*"`
6	`Disallow: https://us.pg.com/health-probe/`	`Pattern should either be empty, start with "/" or "*"`

To appear in search results, crawlers need access to your app.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links are crawlable

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Results for https://pg.com

Site Health

How you compare

Top Priorities (5)

Fix Priority Matrix

Quick Wins

Strategic

Easy Improvements

Deprioritize

What fixing these means

Conversion Barriers

Speed (1)

Trust (2)

Navigation (1)

Return on Investment

Investment

Monthly returns

Regulatory risk avoided

Payback period

Estimated Remediation Cost

Cost by category

Cost by effort level

What Inaction Is Costing You

Compliance Risk

Bandwidth Waste

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Tables and lists

Best Practices

User Experience

General

SEO

Content Best Practices

Crawling and Indexing

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Best Practices

User Experience

General

SEO

Content Best Practices

Crawling and Indexing

Keyboard Shortcuts