americanflatbread.com website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and spotapps.co and others), adding 9.6 MB and 697 ms of main-thread time.

spotapps.co costs a phone 136 ms of main-thread work and 8.9 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.

Your mobile performance score is 53 (desktop: 45). Pages that score under 90 lose visitors before the first paint.

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

2 images could be 258 KiB 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.

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

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

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

13 KiB could be saved by minifying CSS.

24 KiB could be saved by minifying JavaScript.

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.

Your largest element takes 14.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “ABOUT US Food remembers the acts of the hands and heart. Am…”.

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

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

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

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

Scripts block taps and scrolling for 274 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 97 ms to 105 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 1.4 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 17.6 MB in 72 requests on a phone: media 15.0 MB (1), images 1.6 MB (13) and scripts 804 KiB (26). Under 2 MB keeps phones on slow connections fast.

5 images (1.0 MB) 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.

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

4 images are downloaded at several times the size a phone draws them, for example :original at 1,803 px wide, shown at 390 px. Resized copies would save about 482 KiB.

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

Your title is only 18 characters: “American Flatbread”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

There are 12 <h1> headlines (“About us”, “OUR LOCATIONS” and “BRING THE PARTY TO YOU”). One clear main headline is easier for people and search engines.

Your meta description is 372 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 20 pages on americanflatbread.com and 58 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.

/american-flatbread-locations, /american-flatbread-our-culture, /american-flatbread-food-menu, /american-flatbread-drink-menu and /american-flatbread-mobile-oven have no meta description, so Google writes the search snippet from whatever text it finds.

/american-flatbread-food-menu, /american-flatbread-drink-menu and /american-flatbread-mobile-oven 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 7 pages linked from your homepage 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”.

The server only offers HTTP/1.1, so browsers open several connections and load files more slowly. Most hosts and CDNs turn on HTTP/2 with a setting.

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

americanflatbread.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.

americanflatbread.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.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

The homepage has only about 196 words of visible text; thin pages give Google and first-time buyers little to go on.

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.

DMARC is set to p=none, so mail pretending to be americanflatbread.com is still delivered. Add a report address, check the reports, then move to quarantine.

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 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 5 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 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.