1plus1ames.com website review

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

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

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

7 third-party services load with your homepage (Google Tag Manager, jQuery CDN and FontAwesome CDN and others), adding 1.0 MB and 464 ms of main-thread time.

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

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

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

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

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

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

Your largest element takes 3.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Go to Home”.

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

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

4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

There are 2 <h1> headlines (“1+1 Restaurant & Tea - Ames” and “Welcome to 1+1 Restaurant & Tea - Ames”). One clear main headline is easier for people and search engines.

The homepage links to 42 pages on 1plus1ames.com and 20 external pages.

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

robots.txt blocks GPTBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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

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 201 words of visible text; thin pages give Google and first-time buyers little to go on.

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.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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 3 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 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.