Site teardown · Phillips66
phillips66.com
Site health · September 23, 2026
Prepared by Harvv

What your site is actually doing.

One page: what is working, what is costing you visitors, and what to fix next. A phone-and-desktop teardown of the live site: 6 phone loads + 3 desktop loads. No login, no insider access, no Harvv pixel needed. The full evidence is at the bottom.

September 23, 2026·External scan·6 mobile + 3 desktop loads · no pixel data·Download as PDF

Working

What's already working. These held up across every load.

0.8s

Speed is good.

0

No JavaScript errors on load.

100/100

Lighthouse scores SEO 100/100. The fundamentals Google looks for are present.

✓

Nothing spilled past the edge at either 390px (phone) or 1366px (desktop), so the structure is responsive.

Costing you

Ranked by what hurts conversion most. Full evidence below.

41%

Add quotations so AI engines cite this page

faint

Some text is low-contrast and hard to read

20.2MB

Page is heavy and slow on mobile data

tags

Meta Pixel sends only PageView on this page

8

Duplicate title tags

29/32

Images have no width or height set (layout is stable for now)

Fixing next
page weight, duplicate title and image sizes.

3 small changes, on the pages people actually land on: Page is heavy and slow on mobile data; Duplicate title tags; Images have no width or height set (layout is stable for now). We re-measure the same samples after.

4
hours
AI search visibility
How visible is phillips66.com to AI search?
ChatGPT, Perplexity, and Google AI Overviews are the new front page. The AI checks in this report are a preview. A free account turns them into a live 0 to 100 score, tracked daily and benchmarked against your competitors.
See the full AI report, free

01Findings, ranked by what hurts conversion most

SeverityFindingHow we know
MediumPage is heavy and slow on mobile dataBothPerformance
Each visit downloads about 20.2 MB, roughly 19587 KB of images and 869 KB of JavaScript across 108 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.
paste into Claude, Cursor, or ChatGPT
median across loads
LowImages have no width or height set (layout is stable for now)BothPerformanceSEO
29 of 32 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.
paste into Claude, Cursor, or ChatGPT
LowUnused JavaScript is being downloadedBothPerformance
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 288 KiB.
paste into Claude, Cursor, or ChatGPT
LowUnused CSS is being downloadedBothPerformance
Style rules that this page never uses still block rendering while they download. Trimming them frees the paint path. Lighthouse measured: Est savings of 20 KiB.
paste into Claude, Cursor, or ChatGPT
LowThe page loads from a lot of third-party servicesBoth
Around 26 separate outside domains load on this page (analytics, ads, chat widgets, fonts). Each one is a connection that can be slow, fail, or change behavior outside your control.
paste into Claude, Cursor, or ChatGPT
median across loads
LowNo email capture or newsletter detectedBothConversion
No email input field was found in the page, and no email-marketing tag (Klaviyo, Mailchimp, Substack, ConvertKit, Beehiiv, MailerLite, ActiveCampaign, Omnisend, Brevo, Drip or Buttondown) was detected. A form that loads after JavaScript runs, or one behind a popup or a separate page, will not be visible to this check. 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.
paste into Claude, Cursor, or ChatGPT
HighAdd quotations so AI engines cite this pageBothAI SearchSEO
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.)
paste into Claude, Cursor, or ChatGPT
MediumMeta Pixel sends only PageView on this pageBothTracking
On this page the Meta Pixel sends only PageView. That is expected on a homepage, but check that a conversion event (a standard one like Lead, Schedule or Purchase, or a custom event) fires when a visitor actually converts, or that a custom conversion is set up in Events Manager. This scan loads pages and never submits a form or books a call, so it cannot see events that fire on those actions. If nothing fires there, Meta can optimise your ads for page views only.
paste into Claude, Cursor, or ChatGPT
MediumDuplicate title tagsBothSEO
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.)
The exact examples we found:
  • "phillips 66 latest news and company stories" (7 pages)
paste into Claude, Cursor, or ChatGPT
LowNo llms.txt fileBothSEO
No /llms.txt. Optional: some AI tools read this file (Anthropic, Vercel, Stripe, Cloudflare and Hugging Face publish one, and AI coding assistants use it to find docs), so adding one is a cheap courtesy to them. Google has said in writing that Google Search and its AI features do not use llms.txt, so do not expect a search-ranking or AI Overviews benefit from it.
paste into Claude, Cursor, or ChatGPT
HighSome text is low-contrast and hard to readBothAccessibility (WCAG)
LowSecurity headers are missing or weakBothSecurity
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.
paste into Claude, Cursor, or ChatGPT
LowSome text is too small to read on phonesMobileAccessibility (WCAG)Conversion
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.
paste into Claude, Cursor, or ChatGPT
median across loads

Accessibility findings are automated checks against Web Content Accessibility Guidelines (WCAG) 2.1 and 2.2. They flag potential barriers and legal risk, not a certification or a determination of compliance with the ADA, Section 508, or EN 301 549. Automated testing catches only a subset of issues; a full conformance review needs manual and assistive-technology testing by a qualified reviewer.

From finding to fix
Want the fix, not just the finding?
Install Harvv and we turn each issue above into a ready-to-paste prompt for your AI coding assistant. Drop it into Cursor, Claude, or Copilot and the diagnosis becomes a concrete code change, written against this exact page.
Get the fix prompts

"How we know": unlabeled = a deterministic fact, identical on every load (e.g. element sizes). Most findings are this kind, so we only mark the exceptions: median across loads = a noisy lab metric, reported as a median. real-user field data = Google CrUX, actual Chrome visitors.

Structural and AI-search checks crawl up to 8 pages from your sitemap (a sample, not your full site). "Broken" means a link returned 404, 410, or 5xx, or did not respond; access-controlled pages (401, 403) are not counted.

01bTake the whole report to your AI

Every finding above in one payload, with the reasoning behind each one. The prompt is written to be pasted into Claude, Cursor, or ChatGPT. The JSON is for piping into your own tooling.

Includes the site context, what is already working (so your assistant does not "fix" it), and every finding with its severity, evidence, and why it matters.
Audit of https://phillips66.com, run September 23, 2026. 13 issues were found. I want them fixed.

## Context
- Site: https://phillips66.com
- Mobile LCP (lab median): 774 ms
- Desktop LCP (lab median): 760 ms
- Page weight (median): 20.2 MB
- Tap targets under 44px: 10% (12 of 125)
- Evidence base: 6 mobile + 3 desktop loads

## Already working, do not change these
- Speed is good: The main content paints in about 0.8s 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] 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.)

### 2. [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.
Exact elements found: button.wp-block-search__button.wp-element-button "Search": 1:1, needs 4.5:1 (rgb(255, 255, 255) on rgb(255, 255, 255)), h1.wp-block-heading.has-white-color "Providing Energy.Improving L": 1:1, needs 3:1 (rgb(255, 255, 255) on rgb(255, 255, 255)), h2.wp-block-heading "Business Operations": 1:1, needs 3:1 (rgb(255, 255, 255) on rgb(255, 255, 255)), p.wp-block-paragraph "With a focus on continually ": 1:1, needs 4.5:1 (rgb(255, 255, 255) on rgb(255, 255, 255)), button#onetrust-pc-btn-handler: 4.46:1, needs 4.5:1 (rgb(0, 123, 255) on rgb(16, 25, 33))

### 3. [MEDIUM] Page is heavy and slow on mobile data
Category: Performance
Why it matters: Each visit downloads about 20.2 MB, roughly 19587 KB of images and 869 KB of JavaScript across 108 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] Meta Pixel sends only PageView on this page
Category: Tracking
Why it matters: On this page the Meta Pixel sends only PageView. That is expected on a homepage, but check that a conversion event (a standard one like Lead, Schedule or Purchase, or a custom event) fires when a visitor actually converts, or that a custom conversion is set up in Events Manager. This scan loads pages and never submits a form or books a call, so it cannot see events that fire on those actions. If nothing fires there, Meta can optimise your ads for page views only.

### 5. [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)

### 6. [LOW] Images have no width or height set (layout is stable for now)
Category: Performance, SEO
Why it matters: 29 of 32 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 (6 of 29): BAYWAYSTILLS0339.jpeg, 23-0018-HoustonZoo%20%2833%20of%2037%29.jpeg, jg-0401.jpeg, 1112_01A0811.jpeg, BAYWAYSTILLS0165.jpeg, Phillips66-LondonOffice00123.jpeg

### 7. [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 288 KiB.

### 8. [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 20 KiB.

### 9. [LOW] The page loads from a lot of third-party services
Why it matters: Around 26 separate outside domains load on this page (analytics, ads, chat widgets, fonts). Each one is a connection that can be slow, fail, or change behavior outside your control.
How we know: median across loads

### 10. [LOW] No email capture or newsletter detected
Category: Conversion
Why it matters: No email input field was found in the page, and no email-marketing tag (Klaviyo, Mailchimp, Substack, ConvertKit, Beehiiv, MailerLite, ActiveCampaign, Omnisend, Brevo, Drip or Buttondown) was detected. A form that loads after JavaScript runs, or one behind a popup or a separate page, will not be visible to this check. 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.

### 11. [LOW] No llms.txt file
Category: SEO
Why it matters: No /llms.txt. Optional: some AI tools read this file (Anthropic, Vercel, Stripe, Cloudflare and Hugging Face publish one, and AI coding assistants use it to find docs), so adding one is a cheap courtesy to them. Google has said in writing that Google Search and its AI features do not use llms.txt, so do not expect a search-ranking or AI Overviews benefit from it.

### 12. [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.

### 13. [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

## 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.
13 findings, ready to paste

02Performance: phone, desktop, and real visitors

MetricMobileDesktopRead
TTFB (lab median)178 ms181 msLab
FCP (lab median)368 ms384 msLab
LCP (lab median)774 ms760 msGood
Page weight (median)20.2 MB20.2 MBWatch

Google Lighthouse (lab): Performance 57 mobile / 43 desktop, SEO 100, Accessibility 93, Best Practices 100.

Lab numbers are from a headless mobile browser on an unthrottled connection: treat them as a floor, not a typical experience. Add a Google API key to light up real-user field data (CrUX) and Lighthouse scores.

03Tiny buttons are hard to tap on mobile

12 of 125 tappable items on this page come in below the platform minimums for reliable tapping on a phone (Apple recommends 44pt, Android 48dp; WCAG 2.5.8 sets 24px as the hard accessibility floor). The same ones came up small on every one of the 6 test loads, so this is the page itself, not a fluke.

When customers can't tap what they expect to, they get frustrated and many of them leave. They don't file a bug. They don't try again. They just leave. A desktop dashboard can't see this because it's the difference between a thumb and a cursor.

The buttons measuring below the minimum on this scan:

  • button 16x16 "Search"
  • button 16x16 "Menu"
  • a 74x15 "AVIATION"
  • a 192x15 "COMMERCIAL & TRADING"
  • a 192x15 "COMMERCIAL & TRADING"
  • a 90x15 "MIDSTREAM"
  • a 73x15 "REFINING"
  • a 271x15 "SAFETY & OPERATING EXCELLENC"

The fix is CSS-only on most sites: add padding around the icon (don't just change the icon size) so the actual tap area is at least 44×44 pixels. No redesign, no new assets.

04Technical SEO & structured data

CheckResult
TitleLeader in Energy Solutions | Phillips 66 (40 chars)
Meta description108 chars
H11 on page
CanonicalPresent
Structured data (JSON-LD)WebPage
Open GraphTitle + image

05The fix checklist

Everything to fix, priority first, each tagged with the screen it affects and a rough effort. Work top to bottom.

  1. Page is heavy and slow on mobile dataBothSmall
  2. Images have no width or height set (layout is stable for now)BothCSS only
  3. Unused JavaScript is being downloadedBothVaries
  4. Unused CSS is being downloadedBothVaries
  5. The page loads from a lot of third-party servicesBothDev afternoon
  6. No email capture or newsletter detectedBothVaries
  7. Add quotations so AI engines cite this pageBothVaries
  8. Meta Pixel sends only PageView on this pageBothVaries
  9. Duplicate title tagsBoth1 line
  10. No llms.txt fileBothVaries
  11. Some text is low-contrast and hard to readBothVaries
  12. Security headers are missing or weakBothVaries
  13. Some text is too small to read on phonesMobileCSS only

Effort is a rough read from the outside: "CSS only" means no new assets or backend work, "1 line" means a single tag, "Dev afternoon" means a developer needs to touch tracking or scripts.

06What this report cannot tell you

Everything above is from the outside, looking at the page on a simulated phone and desktop. The questions that actually decide revenue need real visitors. Install the Harvv pixel (one script tag, 16 KB, zero personal data, no engineering project) and within about 72 hours you'd know which buttons real customers tapped and missed, how often Google Analytics is missing visits, and exactly where mobile shoppers stalled and left. This report shows you where to look. The pixel shows you how often it happens, and to whom.

What to do next
See this same depth on your real visitors, every day.

Drop the Harvv pixel on phillips66.com and we turn this one-off scan into ongoing measured behavior: which taps miss, where sessions stall, and the real drop rates. Free to start, no card needed.

Add the pixel free

07How we did this, and what it can't prove

  • 6 mobile + 3 desktop loads of one URL from headless Chrome (iPhone viewport at 390px, desktop at 1366px), September 23, 2026. Enough loads to separate real defects from random noise, not a full-site crawl.
  • Lab numbers, not real-user numbers (no field data was available for this run). Real devices on real networks run slower.
  • Friction is inferred, not counted. We can prove a button is small. We can't, from the outside, count how often it causes a missed tap. That requires the pixel on a live page.

About Harvv, the source of this teardown

Harvv is a behavioral UX analytics platform (harvv.com). A lightweight JavaScript pixel captures how real visitors behave on a site (dead clicks, rage clicks, scroll depth, Core Web Vitals, JavaScript errors, and 50+ other signals) and the engine turns them into prioritized, plain-English findings. This teardown is the outside-in version of that: the same detectors run against a public page, with no pixel installed.

How to read it. Every finding here is a reproducible, automated measurement, not an opinion: element sizes, contrast ratios, load metrics, and structured-data checks that anyone can re-run against the same URL. The method is stated in full above. Automated testing catches a subset of issues, so this is a starting point, not a certification.

Full disclosure. Harvv makes the pixel that would measure the friction these findings imply, so we have a commercial interest. That is exactly why the findings are kept to things a reader can verify independently, and why nothing here is inflated: an unreproducible claim would undermine the tool it is meant to demonstrate.

Prepared by Harvv (harvv.com), a behavioral UX analytics platform. Last updated September 23, 2026.

harvv://this-page live
Scroll depth how far you read0%
Dead clicks clicks that did nothing0
Rage clicks frustration bursts0
Interactions clicks that worked0
event log · live