maplestreetbiscuits.com website review

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

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

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

audioeye.com costs a phone 2.2 s of main-thread work and 309 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

8 third-party services load with your homepage (audioeye.com, Squarespace and Google Tag Manager and others), adding 6.0 MB and 3.3 s of main-thread time.

Squarespace costs a phone 674 ms of main-thread work and 4.8 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.

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

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

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

sqspcdn.com costs a phone 94 ms of main-thread work and 420 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.

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

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

Desktop scores 70 but mobile only 41. A gap that wide usually means heavy scripts and images that hit phones hardest.

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 7.8 s on a phone. Good is under 1.8 s.

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

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

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

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

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

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

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

Your homepage downloads 8.7 MB in 155 requests on a phone: images 5.6 MB (27), scripts 2.3 MB (79) and stylesheets 303 KiB (30). Under 2 MB keeps phones on slow connections fast.

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

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

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (1 element).

2 visible links have no text or label, so screen readers cannot say where they go.

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

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

Elements with role="none" or role="presentation" have conflicts (1 element).

Your title is only 28 characters: “Maple Street Biscuit Company”. Between 30 and 65 characters leaves room to say what you do and for whom.

Structured data found (LocalBusiness and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/6489967520aa207907d…”.

The homepage links to 69 pages on maplestreetbiscuits.com and 20 external pages.

Your Organization JSON-LD is missing name, url, logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://www.maplestreetbiscuits.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.

Your homepage links to https://www.maplestreetbiscuits.com/home-seasonal-menu/w4l84t6prbi94ql9gpkzd8328wm77m, https://www.maplestreetbiscuits.com/home-seasonal-menu/dlaxz0ha9eqabbs03tv9jhtqbgq3t9, https://www.maplestreetbiscuits.com/home-seasonal-menu/ngdfldlh6tlr1g5mhfbk5wlocu3wt0, https://www.maplestreetbiscuits.com/home-seasonal-menu/6k0pv50m3pwtxoibaojg69zhftd51f, https://www.maplestreetbiscuits.com/home-seasonal-menu/gi6bvuwclbola5ziqsfqilvpc1x1n2 and https://www.maplestreetbiscuits.com/home-seasonal-menu/0f8ztqdq50alrxzkfgit8aa6rpngk6 and 2 others, which answer with an error. Visitors hit a dead end and search engines drop them.

https://www.maplestreetbiscuits.com/menu, https://www.maplestreetbiscuits.com/locations, https://www.maplestreetbiscuits.com/contact and https://www.maplestreetbiscuits.com/terms-conditions have no <h1> headline, so visitors and search engines get no clear main topic.

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

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

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

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

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

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

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 331 words of visible text.

Before a visitor clicks anything, the page loads 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 1 cookie (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 22 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.