sea2table.com website review

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and rebuyengine.com and others), adding 2.1 MB and 1.8 s of main-thread time.

20 long tasks block the main thread while loading, the longest for 1.6 s. During a long task the page ignores taps.

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

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

Google Tag Manager costs a phone 574 ms of main-thread work and 528 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 126 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.

rebuyengine.com costs a phone 281 ms of main-thread work and 677 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.

Facebook costs a phone 314 ms of main-thread work and 287 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.

The page has 2,384 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

2 KiB could be saved by minifying CSS.

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

3 KiB could be saved by minifying JavaScript.

2 KiB JavaScript is shipped twice across bundles.

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 20.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Wild-Caught American Seafood, Delivered to Your Door Savor …”.

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

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

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

Real visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 260 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

Your homepage downloads 5.5 MB in 376 requests on a phone: scripts 2.3 MB (147), images 1.7 MB (52) and other files 767 KiB (125). Under 2 MB keeps phones on slow connections fast.

2 images further down the page (63 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 1.55 g of CO₂e: 185.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 button has no accessible name, so screen readers announce just “button”.

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

2 frames have no title, so screen-reader users cannot tell what they contain.

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

All page content should be contained by landmarks: 51 elements on the page fail this check, rated moderate by axe-core.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

1 link has no real href, so search engines can't follow it.

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

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 37 pages on sea2table.com and 34 external pages.

/tools/bundle-subscriptions and /tools/bundle-subscriptions/bundle/7421575397537 all use the title “Sea to Table | Wild Caught Seafood Online”. Search engines can't tell which page to show for a search, so each competes with the others.

/tools/bundle-subscriptions, /tools/bundle-subscriptions/bundle/7421575397537, /policies/shipping-policy, /policies/refund-policy, /policies/terms-of-service and /policies/privacy-policy have no meta description, so Google writes the search snippet from whatever text it finds.

/pages/reviews, /tools/bundle-subscriptions, /tools/bundle-subscriptions/bundle/7421575397537 and /pages/faq have no <h1> headline, so visitors and search engines get no clear main topic.

/pages/reviews and /tools/bundle-subscriptions/bundle/7421575397537 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 14 pages linked from your homepage and read each the way a search engine does.

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=5561749&tm=gtm002&Ver=2&mid=46fa02b6-05d2-4328-8b5b-e6ef89bb1b55&bo=1&sid=c2d3fbd0d94411f19d17cd494cca5d1c&vid=c2d43c00d94411f19a5f5de8b5470504&vids=1&msclkid=N&pi=918.

4 errors were logged to the browser console while the page loaded, for example “Identifier 'onClickAccordionHeader' has already been declared”.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

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

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

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

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.

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

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

The homepage carries about 485 words of visible text.

DMARC is set to p=none, so mail pretending to be sea2table.com is still delivered. Reports are on, so moving to quarantine is the next step.

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 Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 4 mores (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 25 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 59 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.