chipotle.com website review

63 files are served with short cache lifetimes, so returning visitors download them again (45.7 MB).

About 2.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 14.4 s faster on a phone.

15 images could be 10.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.7 s faster on a phone.

4 files block the first paint until they finish downloading. Deferring or inlining them could save about 7.7 s.

About 1.1 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 5.5 s faster on a phone.

Your mobile performance score is 39 (desktop: 51). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

A phone's processor spends 4.7 s on main-thread work while loading, 2.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

8 third-party services load with your homepage (sdiapi.com, Google Tag Manager and datadoghq-browser-agent.com and others), adding 579 KiB and 698 ms of main-thread time.

20 long tasks block the main thread while loading, the longest for 423 ms. During a long task the page ignores taps.

Polyfills for old browsers add 59 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

Real visitors wait 6.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

For real visitors the layout shifts by 0.83 (75th percentile). Good is under 0.1.

Real visitors see the first content after 6.2 s (75th percentile). Good is under 1.8 s.

The first text or image appears after 30.3 s on a phone. Good is under 1.8 s.

Your largest element takes 42.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “New flavor lineup just dropped: freshly grilled chicken, ha…”.

Visually, the page fills in at 30.3 s (Speed Index). Good is under 3.4 s.

The page becomes fully interactive after 42.9 s. Good is under 3.8 s.

Scripts block taps and scrolling for 627 ms in total while the page loads. Good is under 200 ms.

Real visitors wait 475 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

11 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 369 ms to 418 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 5.0 s to 5.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 49.5 MB in 119 requests on a phone: media 32.5 MB (9), images 10.5 MB (26) and scripts 4.9 MB (30). Under 2 MB keeps phones on slow connections fast.

M-Secondary-Tout-Chili-Lime-x-Pollo-2x.jpg weighs 829 KiB. On a phone connection a single image that size takes seconds.

3 images (905 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

1 image is downloaded at several times the size a phone draws it, for example M-Secondary-Tout-Chili-Lime-x-Pollo-2x.jpg at 1,176 px wide, shown at 326 px. Resized copies would save about 256 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 14.02 g of CO₂e: 1682.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

ARIA roles used must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

3 tap targets are too small or too close together to hit reliably with a finger.

[role="img"] and [role="image"] elements must have alternative text: 2 elements on the page fail this check, rated serious by axe-core.

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

All page content should be contained by landmarks: 6 elements on the page fail this check, rated moderate by axe-core.

Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (1 element).

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

2 links have no real href, so search engines can't follow them.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 27 pages on chipotle.com and 12 external pages.

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.

There is no /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.

/order/rewards, /order/rewards/exchange and /order/create-account declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

/ and /home all use the title “Mexican Food - Restaurant & Catering - Chipotle Mexican Grill”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

/catering, /order/rewards, /values, /nutrition-calculator, /contact-us and /gift-cards and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

/catering, /values, /gift-cards, /rewards, /sustainability and /responsible-disclosure and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

/values, /contact-us, /gift-cards, /responsible-disclosure and /accessibility have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 15 pages linked from your homepage (of 22 found) and read each the way a search engine does.

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=4022459&tm=gtm002&Ver=2&mid=1a3cf89a-a2ec-4852-a272-eaacef7db911&bo=1&sid=8ff3a5a0c5ce11f181bfb5f771a54aaf&vid=8ff3d840c5ce11f1ab267d2c02d4d5c8&vids=1&msclkid=N&pi=918.

5 of 17 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

4 errors were logged to the browser console while the page loaded, for example “[Datadog] RUM failed to initialize. Check Client Token or App ID.”.

Large scripts ship without source maps.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

chipotle.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

chipotle.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 395 words of visible text.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads FullStory, Google Ads, Google Tag Manager and Microsoft Ads (measured from a US location before any click). A consent tool (Ketch) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 14 cookies (measured from a US location before any click).

Loading the homepage contacts 24 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.