What your site is actually doing.

Audit of https://phillips66.com, run August 16, 2026. 13 issues were found. I want them fixed.

## Context
- Site: https://phillips66.com
- Mobile LCP (lab median): 582 ms
- Desktop LCP (lab median): 576 ms
- Page weight (median): 36.3 MB
- Tap targets under 44px: 8% (10 of 123)
- Evidence base: 4 mobile + 2 desktop loads

## Already working, do not change these
- Speed is good: The main content paints in about 0.6s in our test loads, inside Google's 2.5s "good" threshold. Real networks are slower, but the page itself is not heavy.
- No JavaScript errors on load: Nothing threw a script error across the test loads, so buttons and tracking are not silently breaking mid-session.
- Search basics are in place: Lighthouse scores SEO 100/100. The fundamentals Google looks for are present.
- Layout holds on phone and desktop: Nothing spilled past the edge at either 390px (phone) or 1366px (desktop), so the structure is responsive.

## Issues, most damaging first

### 1. [HIGH] Some text is low-contrast and hard to read
Category: Accessibility (WCAG)
Why it matters: Text that does not stand out enough from its background is hard to read for many visitors, and fails accessibility guidelines Google checks.

### 2. [HIGH] Add quotations so AI engines cite this page
Category: AI Search, SEO
Why it matters: Generative engines (ChatGPT, Perplexity, AI Overviews) lift sourced, attributed quotes almost verbatim, and quotations are the single strongest citation lever (studies measure roughly +41%). Add 1-2 attributed expert quotes or blockquotes to the pages below. (Found across a sample of 8 pages from your sitemap, a partial crawl rather than your full site.)

### 3. [MEDIUM] Page is heavy and slow on mobile data
Category: Performance
Why it matters: Each visit downloads about 36.3 megabytes, roughly 25560 KB of images and 271 KB of JavaScript across 70 separate downloads. On a fast connection that's fine. On a phone with patchy mobile data, that's several seconds of blank screen before the page is readable.
How we know: median across loads

### 4. [MEDIUM] Duplicate title tags
Category: SEO
Why it matters: The same <title> appears on multiple pages. Duplicate titles confuse search engines about which page to rank and split relevance between them. (Found across a sample of 8 pages from your sitemap, a partial crawl rather than your full site.)
Exact examples found: "phillips 66 latest news and company stories" (7 pages)

### 5. [LOW] Images have no width or height set (layout is stable for now)
Category: Performance, SEO
Why it matters: 31 of 33 images don't declare width and height. Your layout currently stays stable (measured Cumulative Layout Shift is 0, which is fine), most likely because space is reserved another way (CSS), so this is not causing visible jumps today. It is still worth setting explicit dimensions or a CSS aspect-ratio so a slow connection or a future style change cannot reintroduce shift.
Exact elements found: BAYWAYSTILLS0339.jpeg, 23-0018-HoustonZoo%20%2833%20of%2037%29.jpeg, jg-0401.jpeg, 1112_01A0811.jpeg, BAYWAYSTILLS0165.jpeg, Phillips66-LondonOffice00123.jpeg

### 6. [LOW] Security headers are missing or weak
Category: Security
Why it matters: The server response is missing browser-hardening headers that protect visitors and are a standard security and agency checklist item. Missing or weak here: Content-Security-Policy (the main defense against injected and cross-site scripts); a stronger HSTS policy (max-age at least 180 days plus includeSubDomains). These are set at the server, CDN, or host level (most platforms expose them in settings or a config file) and do not change how the site looks or performs.

### 7. [LOW] Some text is too small to read on phones
Affects: mobile only
Category: Accessibility (WCAG), Conversion
Why it matters: 61 chunks of text come in under 12 pixels on this page. Most visitors don't zoom, they just skim past anything that small. Bumping the smallest body text to 14 pixels makes the page read without effort.
How we know: median across loads

### 8. [LOW] No advertising pixel detected
Category: Tracking
Why it matters: Analytics is present but no Meta/Google/TikTok ad pixel was found. If you run paid ads, conversion tracking should be installed before the next campaign so the platforms can optimize toward buyers, not clicks.

### 9. [LOW] No email capture or newsletter detected
Category: Conversion
Why it matters: No email-marketing tag (Klaviyo, Mailchimp, etc.) was found. If capturing visitors is relevant to this site, an email signup builds an owned audience you keep regardless of ad costs. Not every site needs one.

### 10. [LOW] No visible contact details (email or phone)
Category: Conversion
Why it matters: The page exposes no email or phone link. For higher-value or trust-sensitive purchases, a clear way to reach a human reduces hesitation. Add an email or phone link in the header or footer.

### 11. [LOW] Unused JavaScript is being downloaded
Category: Performance
Why it matters: Code that never runs on this page still costs download and parse time on every visit. Splitting or removing it speeds up load. Lighthouse measured: Est savings of 133 KiB.

### 12. [LOW] Unused CSS is being downloaded
Category: Performance
Why it matters: Style rules that this page never uses still block rendering while they download. Trimming them frees the paint path. Lighthouse measured: Est savings of 18 KiB.

### 13. [LOW] No llms.txt file
Category: SEO
Why it matters: No /llms.txt. This emerging standard gives AI search engines a clean, structured map of your most important content, improving how they understand and cite your site.

## How to respond
Work through the issues in order. For each one give me the specific change that fixes it: real code or real copy, not advice. Keep changes minimal and match the existing style of the site.
Where several issues share one root cause, say so and fix it once rather than patching each symptom.
If an issue cannot be fixed without seeing more of the code, say exactly which file or selector you need instead of guessing.

{
  "generated_by": "Harvv",
  "report_url": "https://phillips66.com",
  "generated_at": "2026-08-21T19:25:48.397Z",
  "evidence_base": {
    "mobile_loads": 4,
    "desktop_loads": 2,
    "field_data": false,
    "lighthouse": true
  },
  "performance": {
    "mobile_lcp_ms": 582,
    "desktop_lcp_ms": 576,
    "mobile_ttfb_ms": 185,
    "mobile_fcp_ms": 312,
    "page_weight_kb": 37168
  },
  "finding_count": 13,
  "findings": [
    {
      "severity": "high",
      "title": "Some text is low-contrast and hard to read",
      "detail": "Text that does not stand out enough from its background is hard to read for many visitors, and fails accessibility guidelines Google checks.",
      "device": "both",
      "tags": [
        "Accessibility (WCAG)"
      ],
      "topic": "contrast",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "high",
      "title": "Add quotations so AI engines cite this page",
      "detail": "Generative engines (ChatGPT, Perplexity, AI Overviews) lift sourced, attributed quotes almost verbatim, and quotations are the single strongest citation lever (studies measure roughly +41%). Add 1-2 attributed expert quotes or blockquotes to the pages below. (Found across a sample of 8 pages from your sitemap, a partial crawl rather than your full site.)",
      "device": "both",
      "tags": [
        "AI Search",
        "SEO"
      ],
      "topic": "geo",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "medium",
      "title": "Page is heavy and slow on mobile data",
      "detail": "Each visit downloads about 36.3 megabytes, roughly 25560 KB of images and 271 KB of JavaScript across 70 separate downloads. On a fast connection that's fine. On a phone with patchy mobile data, that's several seconds of blank screen before the page is readable.",
      "device": "both",
      "tags": [
        "Performance"
      ],
      "topic": "page_weight",
      "confidence": "sampled",
      "evidence": []
    },
    {
      "severity": "medium",
      "title": "Duplicate title tags",
      "detail": "The same <title> appears on multiple pages. Duplicate titles confuse search engines about which page to rank and split relevance between them. (Found across a sample of 8 pages from your sitemap, a partial crawl rather than your full site.)",
      "device": "both",
      "tags": [
        "SEO"
      ],
      "topic": "duplicate_title",
      "confidence": "measured",
      "evidence": [
        "\"phillips 66 latest news and company stories\" (7 pages)"
      ]
    },
    {
      "severity": "low",
      "title": "Images have no width or height set (layout is stable for now)",
      "detail": "31 of 33 images don't declare width and height. Your layout currently stays stable (measured Cumulative Layout Shift is 0, which is fine), most likely because space is reserved another way (CSS), so this is not causing visible jumps today. It is still worth setting explicit dimensions or a CSS aspect-ratio so a slow connection or a future style change cannot reintroduce shift.",
      "device": "both",
      "tags": [
        "Performance",
        "SEO"
      ],
      "topic": "image_dims",
      "confidence": "measured",
      "evidence": [
        "BAYWAYSTILLS0339.jpeg",
        "23-0018-HoustonZoo%20%2833%20of%2037%29.jpeg",
        "jg-0401.jpeg",
        "1112_01A0811.jpeg",
        "BAYWAYSTILLS0165.jpeg",
        "Phillips66-LondonOffice00123.jpeg"
      ]
    },
    {
      "severity": "low",
      "title": "Security headers are missing or weak",
      "detail": "The server response is missing browser-hardening headers that protect visitors and are a standard security and agency checklist item. Missing or weak here: Content-Security-Policy (the main defense against injected and cross-site scripts); a stronger HSTS policy (max-age at least 180 days plus includeSubDomains). These are set at the server, CDN, or host level (most platforms expose them in settings or a config file) and do not change how the site looks or performs.",
      "device": "both",
      "tags": [
        "Security"
      ],
      "topic": "security_headers",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "Some text is too small to read on phones",
      "detail": "61 chunks of text come in under 12 pixels on this page. Most visitors don't zoom, they just skim past anything that small. Bumping the smallest body text to 14 pixels makes the page read without effort.",
      "device": "mobile",
      "tags": [
        "Accessibility (WCAG)",
        "Conversion"
      ],
      "topic": "tiny_text",
      "confidence": "sampled",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "No advertising pixel detected",
      "detail": "Analytics is present but no Meta/Google/TikTok ad pixel was found. If you run paid ads, conversion tracking should be installed before the next campaign so the platforms can optimize toward buyers, not clicks.",
      "device": "both",
      "tags": [
        "Tracking"
      ],
      "topic": "no_ad_pixel",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "No email capture or newsletter detected",
      "detail": "No email-marketing tag (Klaviyo, Mailchimp, etc.) was found. If capturing visitors is relevant to this site, an email signup builds an owned audience you keep regardless of ad costs. Not every site needs one.",
      "device": "both",
      "tags": [
        "Conversion"
      ],
      "topic": "no_email_capture",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "No visible contact details (email or phone)",
      "detail": "The page exposes no email or phone link. For higher-value or trust-sensitive purchases, a clear way to reach a human reduces hesitation. Add an email or phone link in the header or footer.",
      "device": "both",
      "tags": [
        "Conversion"
      ],
      "topic": "no_contact",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "Unused JavaScript is being downloaded",
      "detail": "Code that never runs on this page still costs download and parse time on every visit. Splitting or removing it speeds up load. Lighthouse measured: Est savings of 133 KiB.",
      "device": "both",
      "tags": [
        "Performance"
      ],
      "topic": "unused_js",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "Unused CSS is being downloaded",
      "detail": "Style rules that this page never uses still block rendering while they download. Trimming them frees the paint path. Lighthouse measured: Est savings of 18 KiB.",
      "device": "both",
      "tags": [
        "Performance"
      ],
      "topic": "unused_css",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "No llms.txt file",
      "detail": "No /llms.txt. This emerging standard gives AI search engines a clean, structured map of your most important content, improving how they understand and cite your site.",
      "device": "both",
      "tags": [
        "SEO"
      ],
      "topic": "missing_llms_txt",
      "confidence": "measured",
      "evidence": []
    }
  ]
}