Site teardown · Pbfenergy

Pbfenergy: a phone-and-desktop teardown

We loaded https://pbfenergy.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.

June 16, 2026·External scan·3 mobile + 2 desktop loads · no pixel data·Download as PDF

TL;DRWhat jumped out

Of everything we found on this scan, this is the one to start with: Tiny buttons are hard to tap on mobile. 26 of 33 tappable items on this page come in below 44×44 pixels, the minimum size Apple and Google recommend for reliable tapping, and the same ones came up small on every test load. When visitors can't hit what they expect to, they get frustrated and many of them leave instead of trying again.

79%

Tap targets under the 44px minimum (26 of 33)

496ms

Largest contentful paint (lab median)

0.7 MB

Total page weight (median)

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.5s in our test loads, inside Google's 2.5s "good" threshold. Real networks are slower, but the page itself is not heavy.
Light page weight. The page is about 0.7 MB across 68 requests. That keeps it quick on mobile data and cheap to load repeatedly.
No JavaScript errors on load. Nothing threw a script error across the test loads, so buttons and tracking are not silently breaking mid-session.
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	Tiny buttons are hard to tap on mobileMobile 26 of 33 tappable items on this page come in below 44×44 pixels, the minimum size Apple and Google recommend for reliable tapping, and the same ones came up small on every test load. When visitors can't hit what they expect to, they get frustrated and many of them leave instead of trying again.	identical every load
High	Google Analytics tracking brokenBoth The Google Analytics request failed to complete on every one of the 3 test loads. If real visitors hit the same failure, GA is missing those visits and the dashboard has no way to flag it. Conversion numbers, audience counts, and channel attribution are all undercounting. Worth checking the tag loading order and any consent banner that might be blocking the request.	identical every load
Low	Search-result title is leaving room on the tableBoth Google gives you about 60 characters of headline space in search results. This page is using 17. Adding the value proposition or a relevant keyword gives someone one more reason to click.	identical every load

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": 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)	126 ms	132 ms	Lab
FCP (lab median)	412 ms	372 ms	Lab
LCP (lab median)	496 ms	456 ms	Good
Page weight (median)	0.7 MB	0.7 MB	OK

Google Lighthouse (lab): Performance 63 mobile / 98 desktop, SEO 85, Accessibility 84, 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

26 of 33 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.

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:

a 1x1 "Skip to content"
div 33x33 "Menu Toggle"
button 73x40 "Submit"
a 350x31 "About Us"
a 46x24 "Safety"
a 133x24 "Management Team"
a 130x24 "Board of Directors"
a 62x31 "Careers"

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	Home - PBF Energy (17 chars)
Meta description	158 chars
H1	1 on page
Canonical	Present
Structured data (JSON-LD)	1 block(s)
Open Graph	Incomplete

05The fix checklist

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

Tiny buttons are hard to tap on mobileMobileCSS only
Google Analytics tracking brokenBothDev afternoon
Search-result title is leaving room on the tableBoth1 line

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 pbfenergy.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

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.