Website review, no card needed
pepsico.com website review
Visit site (opens in a new tab)Reviewed 25 October 202625 issues · 72 checks
This review found 25 issues worth fixing on pepsico.com, 12 of them high impact, across 72 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
79CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.5 s |
| May 9, 2026 | 1.6 s |
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 115 ms |
| May 9, 2026 | 118 ms |
| May 16, 2026 | 194 ms |
| May 23, 2026 | 198 ms |
| May 30, 2026 | 198 ms |
| Jun 6, 2026 | 202 ms |
| Jun 13, 2026 | 178 ms |
| Jun 20, 2026 | 176 ms |
| Jun 27, 2026 | 156 ms |
| Jul 4, 2026 | 152 ms |
| Jul 11, 2026 | 163 ms |
| Jul 18, 2026 | 160 ms |
| Jul 25, 2026 | 176 ms |
| Aug 1, 2026 | 177 ms |
| Aug 8, 2026 | 171 ms |
| Aug 15, 2026 | 170 ms |
| Aug 22, 2026 | 169 ms |
| Aug 29, 2026 | 163 ms |
| Sep 5, 2026 | 163 ms |
| Sep 12, 2026 | 166 ms |
| Sep 19, 2026 | 162 ms |
| Sep 26, 2026 | 163 ms |
| Oct 3, 2026 | 163 ms |
| Oct 10, 2026 | 165 ms |
| Oct 17, 2026 | 167 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.2 s
1.6 s
2.1 s
2.5 s
2.9 s
3.3 s
Speed
Use efficient cache lifetimes
4.0 s · 1.9 MB35 files are served with short cache lifetimes, so returning visitors download them again (1.9 MB).
Improve image delivery
3.7 s · 1.6 MB18 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.7 s faster on a phone.
Reduce unused JavaScript
2.0 s · 351 KiBAbout 351 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.0 s faster on a phone.
Mobile performance score: 56
56/100Your mobile performance score is 56 (desktop: 92). Pages that score under 90 lose visitors before the first paint.
Main-thread work: 2.3 s
A phone's processor spends 2.3 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3 third-party services on the page
3 third-party services load with your homepage (Google Tag Manager, securiti.ai and joy-pepsico.eu), adding 311 KiB and 240 ms of main-thread time.
Legacy JavaScript
200 ms · 21 KiBPolyfills for old browsers add 21 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Render-blocking requests
150 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 124 ms. During a long task the page ignores taps.
Reduce unused CSS
50 ms · 11 KiBAbout 11 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 50 ms faster on a phone.
Phones get a much slower page than desktops
Desktop scores 92 but mobile only 56. A gap that wide usually means heavy scripts and images that hit phones hardest.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 19 ms
19 msYour server sent the HTML in 19 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Largest Contentful Paint: 13.9 s
13.9 sYour largest element takes 13.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “FDS REFORMAT”.
Time to Interactive: 13.9 s
13.9 sThe page becomes fully interactive after 13.9 s. Good is under 3.8 s.
Speed Index: 8.6 s
8.6 sVisually, the page fills in at 8.6 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.5 s
3.5 sThe first text or image appears after 3.5 s on a phone. Good is under 1.8 s.
Real-user INP: 213 ms
213 msReal visitors wait 213 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 42% slower for real visitors
+42%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 115 ms to 167 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 35% slower for real visitors
+35%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.5 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 872 ms
872 msReal visitors wait 872 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 234 ms
234 msScripts block taps and scrolling for 234 ms in total while the page loads. Good is under 200 ms.
4 checks passed
Real-user LCP: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 10.0 MB in 90 requests
10.0 MBYour homepage downloads 10.0 MB in 90 requests on a phone: media 6.7 MB (16), images 2.0 MB (33) and scripts 729 KiB (16). Under 2 MB keeps phones on slow connections fast.
8 images far larger than shown
839 KiB8 images are downloaded at several times the size a phone draws them, for example PEPSICO_07_TOSTITOS_-6_07671-1 at 812 px wide, shown at 106 px. Resized copies would save about 839 KiB.
2 images below the first screen load straight away
2 images further down the page (162 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.8 g of CO₂ per visit
2.84 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.84 g of CO₂e: 340.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
1 checks passed
Every image has alt text
All 18 images in the HTML carry an alt attribute.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
48 internal links, 20 external
The homepage links to 48 pages on pepsico.com and 20 external pages.
7 checks passed
Meta description: 142 characters
Your meta description is 142 characters: “Experience the taste and energy of PepsiCo. Explore our iconic brands, delicious innovations, and the smiles we serve w…”.
One H1 headline
Your main headline reads: “Find Your Faves”.
Title: 40 characters
Your title is a healthy 40 characters: “PepsiCo | Food and Drinks to Smile About”.
Canonical URL set
The canonical URL is https://www.pepsico.com/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.pepsico.com/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://www.pepsico.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
2 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (279 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 34 found) and read each the way a search engine does.
7 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
28 of 28 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 272 words of copy
The homepage carries about 272 words of visible text.
2 checks passed
5 calls to action
The homepage has 5 calls to action, for example “Contact”, “Learn more” and “Contact Us”.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
3 cookies set on arrival
3Opening the homepage sets 3 cookies (measured from a US location before any click).
No consent tool detected
No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.
4 other companies contacted
Loading the homepage contacts 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at pepsico.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
Company
- Employees
- 309,000
- Founded
- 1961
- Headquarters
- Purchase
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 25 issues on pepsico.com, including 15 speed issues, 1 SEO issue and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.