Website review, no card needed

einsteinbros.com logo

einsteinbros.com website review

Visit site (opens in a new tab)Reviewed 30 October 202633 issues · 85 checks

This review found 33 issues worth fixing on einsteinbros.com, 5 of them high impact, across 85 checks. The most urgent: page weight: 4.2 MB in 169 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
671 ms455 msMay 9Oct 24523 ms
Show as table
DateReal-visitor load time (LCP)
May 9, 2026638 ms
May 16, 2026643 ms
May 23, 2026646 ms
May 30, 2026641 ms
Jun 6, 2026623 ms
Jun 13, 2026594 ms
Jun 20, 2026559 ms
Jun 27, 2026526 ms
Jul 4, 2026501 ms
Jul 11, 2026487 ms
Jul 18, 2026480 ms
Jul 25, 2026482 ms
Aug 1, 2026496 ms
Aug 8, 2026516 ms
Aug 15, 2026532 ms
Aug 22, 2026545 ms
Aug 29, 2026548 ms
Sep 5, 2026549 ms
Sep 12, 2026549 ms
Sep 19, 2026547 ms
Sep 26, 2026546 ms
Oct 3, 2026540 ms
Oct 10, 2026536 ms
Oct 17, 2026528 ms
Oct 24, 2026523 ms
Real-visitor tap response (INP)75th percentile, phones
191 ms120 msMay 9Oct 24183 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026136 ms
May 16, 2026134 ms
May 23, 2026130 ms
May 30, 2026129 ms
Jun 6, 2026128 ms
Jun 13, 2026128 ms
Jun 20, 2026128 ms
Jun 27, 2026128 ms
Jul 4, 2026128 ms
Jul 11, 2026128 ms
Jul 18, 2026128 ms
Jul 25, 2026129 ms
Aug 1, 2026130 ms
Aug 8, 2026137 ms
Aug 15, 2026144 ms
Aug 22, 2026146 ms
Aug 29, 2026148 ms
Sep 5, 2026147 ms
Sep 12, 2026149 ms
Sep 19, 2026154 ms
Sep 26, 2026162 ms
Oct 3, 2026171 ms
Oct 10, 2026179 ms
Oct 17, 2026182 ms
Oct 24, 2026183 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

Full-page screenshot of einsteinbros.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. einsteinbros.com at 0.4 s0.4 s
  2. einsteinbros.com at 0.8 s0.8 s
  3. einsteinbros.com at 1.1 s1.1 s
  4. einsteinbros.com at 1.5 s1.5 s
  5. einsteinbros.com at 1.9 s1.9 s
  6. einsteinbros.com at 2.3 s2.3 s
  7. einsteinbros.com at 2.6 s2.6 s
  8. einsteinbros.com at 3.0 s3.0 s

Speed

9 to fix66
  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Google Tag Manager and Facebook and others), adding 1.8 MB and 1.1 s of main-thread time.

  • Reduce unused JavaScript

    150 ms · 932 KiB

    About 932 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Mobile performance score: 66

    66/100

    Your mobile performance score is 66. Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    750 ms

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.

  • Use efficient cache lifetimes

    422 KiB

    16 files are served with short cache lifetimes, so returning visitors download them again (422 KiB).

  • Google CDN adds 337 ms

    337 ms

    Google CDN costs a phone 337 ms of main-thread work and 741 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Reduce unused CSS

    300 ms · 88 KiB

    About 88 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Google Tag Manager adds 265 ms

    265 ms

    Google Tag Manager costs a phone 265 ms of main-thread work and 364 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Main-thread work: 2.7 s

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

  • 10 long tasks on the main thread

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

  • Improve image delivery

    150 ms · 63 KiB

    6 images could be 63 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • Legacy JavaScript

    36 KiB

    Polyfills for old browsers add 36 KiB JavaScript that modern phones do not need.

  • Chained critical requests

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

1 checks passed
  • Server response: 6 ms

    6 ms

    Your server sent the HTML in 6 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix100
  • Time to Interactive: 22.0 s

    22.0 s

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

  • Largest Contentful Paint: 5.6 s

    5.6 s

    Your largest element takes 5.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Tap response (INP) got 35% slower for real visitors

    +35%

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

  • Total Blocking Time: 380 ms

    380 ms

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

  • Speed Index: 3.9 s

    3.9 s

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 0.7 s

    0.7 s

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

  • Real-user INP: 147 ms

    147 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 0.7 s

    0.7 s

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

  • Real-user TTFB: 337 ms

    337 ms

    Real visitors wait 337 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 18% faster for real visitors

    -18%

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

  • Cumulative Layout Shift: 0.067

    0.067

    The layout barely moves while loading (CLS 0.067, good is under 0.1).

Images and page weight

1 to fix70
  • Page weight: 4.2 MB in 169 requests

    4.2 MB

    Your homepage downloads 4.2 MB in 169 requests on a phone: scripts 2.2 MB (64), images 1.3 MB (46) and other files 418 KiB (41). Under 2 MB keeps phones on slow connections fast.

  • 2 images below the first screen load straight away

    2 images further down the page (51 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.2 g of CO₂ per visit

    1.20 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

8 to fixGoogle 9492
  • 1 text element with low contrast

    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 (2 elements)

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

  • Contentinfo landmark should not be contained in another landmark (1 element)

    Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one banner landmark (1 element)

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

  • Document should not have more than one contentinfo landmark (1 element)

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

  • The skip-link target should exist and be focusable (1 element)

    The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 42 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10090
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • 71 internal links, 65 external

    The homepage links to 71 pages on einsteinbros.com and 65 external pages.

7 checks passed
  • Meta description: 121 characters

    Your meta description is 121 characters: “Craveable fresh-baked bagels & breakfast egg sandwiches at Einstein Bros. Bagels. Order online or find a bakery near yo…”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “Einstein Bros. Bagels | Fresh-Baked for Breakfast Near You”.

  • Canonical URL set

    The canonical URL is https://www.einsteinbros.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, Restaurant and WebPage.

  • 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.einsteinbros.com/sitemap_index.xml.

AI search readiness

100
4 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.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (550 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.einsteinbros.com/llms.txt (4 KiB, 39 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix88
  • 2 pages without a meta description

    https://www.einsteinbros.com/careers and https://www.einsteinbros.com/franchise have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages share a meta description

    https://www.einsteinbros.com/menu/featured/8-breakfast-brew, https://www.einsteinbros.com/menu, https://www.einsteinbros.com/menu/breakfast/signature-egg-sandwiches/farmhouse-egg-sandwich, https://www.einsteinbros.com/menu/beverages/iced-coffee-tea, https://www.einsteinbros.com/menu/breakfast/signature-egg-sandwiches/bacon-avocado-tomato-egg-white-sandwich and https://www.einsteinbros.com/menu/beverages/iced-coffee-tea/new-classic-iced-coffee use the same meta description. A description written for each page earns more clicks.

  • 5 links to non-canonical URLs

    Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://www.einsteinbros.com/menu/featured/8-breakfast-brew, whose canonical is https://www.einsteinbros.com/menu. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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

1 to fixGoogle 9693
  • 19 small tap targets

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix75
  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

    Social proof on the homepage: 4 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • A 10-field form

    Your longest form asks for 10 fields (10 required). Every extra field lowers completion.

  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 350 words of copy

    The homepage carries about 350 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Try our $8 breakfast and brew! NEW” and “ORDER NOW”.

  • 20 calls to action

    The homepage has 20 calls to action, for example “Order Now”, “Join Rewards” and “BUY GIFT CARDS”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

  • 7 trackers load before any consent

    7

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

  • 12 cookies set on arrival

    12

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

  • 31 other companies contacted

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

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

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 einsteinbros.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Tag Manager
Hosting
Fastly

Company

Founded
1995
Headquarters
Lakewood

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on einsteinbros.com, including 15 speed issues, 1 SEO issue and 4 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25