Phillips66: a phone-and-desktop teardown
We loaded https://phillips66.com 3 times on a simulated iPhone and 2 more on a 1366px desktop, and wrote down what a real visitor would see on each. No login, no insider access, no Harvv pixel needed. Here is what repeated visits already show, sorted by how we know it.
TL;DRWhat jumped out
Of everything we found on this scan, this is the one to start with: Images without sizes set make the page jump as it loads. 31 of 33 images on this page don't have width and height set. As each image finishes loading, the content below it slides down to make room. The visitor goes to tap one thing and ends up tapping another, and the cause is invisible to them.
Below: what's already working, every finding ranked by impact and tagged with the screen it affects, the speed numbers on phone and desktop, and a checklist of what to fix first.
00What's already working
Start here so the problems below are in context. These held up across the test loads:
- Speed is good. The main content paints in about 0.7s 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.
01Findings, ranked by what hurts conversion most
| Severity | Finding | How we know |
|---|---|---|
| High | Images without sizes set make the page jump as it loadsBoth 31 of 33 images on this page don't have width and height set. As each image finishes loading, the content below it slides down to make room. The visitor goes to tap one thing and ends up tapping another, and the cause is invisible to them. | identical every load |
| Medium | Page is heavy and slow on mobile dataBoth Each visit downloads about 35.2 megabytes — roughly 24434 KB of images and 266 KB of JavaScript across 69 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. | median across loads |
| Low | Some text is too small to read on phonesMobile 60 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. | median across loads |
"How we know": identical every load = a deterministic fact (e.g. element sizes). median across loads = a noisy lab metric, reported as a median. real-user field data = Google CrUX, actual Chrome visitors.
02Performance: phone, desktop, and real visitors
| Metric | Mobile | Desktop | Read |
|---|---|---|---|
| TTFB (lab median) | 236 ms | 214 ms | Lab |
| FCP (lab median) | 384 ms | 424 ms | Lab |
| LCP (lab median) | 700 ms | 756 ms | Good |
| Page weight (median) | 35.2 MB | 35.2 MB | Watch |
Google Lighthouse (lab): Performance 70 mobile / 77 desktop, SEO 100, Accessibility 88, 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
23 of 122 tappable items on this page come in below 44×44 pixels, the size Apple and Google both recommend for reliable tapping on a phone. The same ones came up small on every one of the 3 test loads, so this is the page itself, not a fluke.
The buttons measuring below the minimum on this scan:
- a 42x62 "Return to homepage"
- button 16x16 "Search"
- button 16x16 "Menu"
- a 74x15 "AVIATION"
- a 253x35 "FUELS, LUBRICANTS & CHEMICAL"
- a 74x15 "AVIATION"
- a 253x35 "FUELS, LUBRICANTS & CHEMICAL"
- a 90x15 "MIDSTREAM"
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
| Check | Result |
|---|---|
| Title | Leader in Energy Solutions | Phillips 66 (40 chars) |
| Meta description | 108 chars |
| H1 | 1 on page |
| Canonical | Present |
| Structured data (JSON-LD) | WebPage |
| Open Graph | Title + image |
05The fix checklist
Everything to fix, priority first, each tagged with the screen it affects and a rough effort. Work top to bottom.
- Images without sizes set make the page jump as it loadsBothCSS only
- Page is heavy and slow on mobile dataBothCSS only
- 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.
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 free07How we did this, and what it can't prove
- 3 mobile + 2 desktop loads of one URL from headless Chrome (iPhone viewport at 390px, desktop at 1366px), June 16, 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.
Prepared by Harvv. Last updated June 16, 2026.