macrinabakery.com website review

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

About 967 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.7 s faster on a phone.

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

11 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

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

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

Squarespace costs a phone 705 ms of main-thread work and 1.3 MB 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.

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

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

Google Tag Manager costs a phone 295 ms of main-thread work and 462 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.

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 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.

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

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

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

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

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

6 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-17, real Chrome visitors' tap response (inp) went from 88 ms to 91 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 10.6 MB in 121 requests on a phone: images 8.1 MB (34), scripts 1.9 MB (47) and fonts 305 KiB (15). Under 2 MB keeps phones on slow connections fast.

3 images weigh 2.4 MB together. On a phone connection a single image that size takes seconds.

5 images are downloaded at several times the size a phone draws them, for example Basque_cheesecake_ROM_2024_FEB_H.jpg at 2,500 px wide, shown at 495 px. Resized copies would save about 1.8 MB.

23 images further down the page (4.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

mag1.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

All page content should be contained by landmarks: 17 elements on the page fail 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, h1 → h3 and h1 → h3), which makes the page harder to scan with a screen reader.

No meta description, so Google writes its own snippet from whatever text it finds.

There are 7 <h1> headlines (“ORDER NOW FOR PICKUP OR DELIVERY”, “Pre-Order Now for Pickup!” and “Get a FREE Loaf”). One clear main headline is easier for people and search engines.

Structured data found (WebSite) but with 1 problem, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/5dcf312bedd4622bff8…”.

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

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 45 pages on macrinabakery.com and 26 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 https://macrinabakery.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.

https://macrinabakery.com/history-and-accolades, https://macrinabakery.com/meet-our-team, https://macrinabakery.com/wholesale, https://macrinabakery.com/retailers, https://macrinabakery.com/jobs and https://macrinabakery.com/contact-us and 9 others all use the title “Macrina Bakery - Seattle's favorite bakery since 1993.”. Search engines can't tell which page to show for a search, so each competes with the others.

https://macrinabakery.com/history-and-accolades, https://macrinabakery.com/meet-our-team, https://macrinabakery.com/wholesale, https://macrinabakery.com/retailers, https://macrinabakery.com/jobs and https://macrinabakery.com/contact-us and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://macrinabakery.com/aloha-cafe, https://macrinabakery.com/belltown-cafe, https://macrinabakery.com/kent-cafe, https://macrinabakery.com/maple-leaf-cafe, https://macrinabakery.com/mcgraw-cafe and https://macrinabakery.com/mercer-island-cafe and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

The homepage carries about 385 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.

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

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.

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