tablefor12.studio website review

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Listrak and bookthatapp.com and others), adding 1.6 MB and 394 ms of main-thread time.

8 images could be 323 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

Shopify costs a phone 22 ms of main-thread work and 626 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.

43 KiB could be saved by minifying JavaScript.

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

About 10 KiB of CSS is downloaded but never applied on this page.

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.

4 KiB could be saved by minifying CSS.

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

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

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

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

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

Your homepage downloads 3.2 MB in 256 requests on a phone: scripts 1.1 MB (90), images 938 KiB (16) and other files 827 KiB (98). Under 2 MB keeps phones on slow connections fast.

Parisian_2.jpg 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).

1 image (104 KiB) is 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.

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

1 frame has no title, so screen-reader users cannot tell what it contains.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

2 images have no alt text, which hurts accessibility and image search.

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

Headings should not be empty: 4 elements on the page fail this check, rated minor by axe-core.

Headings skip levels (h3 → h5), 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.

Your title is only 12 characters: “Table For 12”. Between 30 and 65 characters leaves room to say what you do and for whom.

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

Your <h1> is empty.

The homepage links to 47 pages on tablefor12.studio and 10 external pages.

There is no https://tablefor12.studio/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.

/ and https://tablefor12.studio/apps/bookthatapp/calendar all use the title “Table For 12”. Search engines can't tell which page to show for a search, so each competes with the others.

https://tablefor12.studio/collections/all, https://tablefor12.studio/apps/bookthatapp/calendar, https://tablefor12.studio/pages/private-events and https://tablefor12.studio/pages/faq have no meta description, so Google writes the search snippet from whatever text it finds.

https://tablefor12.studio/collections/all, https://tablefor12.studio/apps/bookthatapp/calendar, https://tablefor12.studio/pages/private-events and https://tablefor12.studio/pages/faq have no <h1> headline, so visitors and search engines get no clear main topic.

https://tablefor12.studio/apps/bookthatapp/calendar has 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 14 pages linked from your homepage and read each the way a search engine does.

6 errors were logged to the browser console while the page loaded, for example “Failed to find a valid digest in the 'integrity' attribute for resource 'https://cdnjs.cloudflare.com/ajax/libs/moment.…”.

Chrome logged issues while loading the page (“Cookie”).

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

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

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