shaggys.com website review

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

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

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

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

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

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

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

8 third-party services load with your homepage (Facebook, review-alerts.com and Google Tag Manager and others), adding 1.2 MB and 959 ms of main-thread time.

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

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

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

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

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

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.

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

Your largest element takes 33.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 34.7 s. Good is under 3.8 s.

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

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

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

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

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

Real visitors wait 1.4 s for your server to start answering (75th percentile). Good is under 800 ms.

14 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-10, real Chrome visitors' largest content (lcp) went from 2.7 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 7.8 MB in 140 requests on a phone: images 4.2 MB (15), scripts 2.1 MB (66) and fonts 1.1 MB (14). Under 2 MB keeps phones on slow connections fast.

Crab-2.jpg weighs 627 KiB. On a phone connection a single image that size takes seconds.

3 images (1,019 KiB) 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.

1 image is downloaded at several times the size a phone draws it, for example S7-Crab-House-Logo-1-scaled.png at 2,400 px wide, shown at 165 px. Resized copies would save about 194 KiB.

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

Elements must only use permitted ARIA attributes: 15 elements on the page fail this check, rated serious by axe-core.

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

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

No XML sitemap at https://shaggys.com/sitemap.xml, so Google discovers your pages only by following links.

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

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

The homepage links to 98 pages on shaggys.com and 16 external pages.

The HTML your server sends has 542 of the 1,227 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

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

https://shaggys.com/private-events and https://shaggys.com/private-parties all use the title “Private Parties • Shaggys Restaurants 2026 Fun At Shaggy's!”. Search engines can't tell which page to show for a search, so each competes with the others.

https://shaggys.com/private-events and https://shaggys.com/private-parties use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://shaggys.com/private-events, whose canonical is https://shaggys.com/private-parties. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://shaggys.com/private-events and https://shaggys.com/locations/gulfport-beach took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://shaggys.com/.

5 errors were logged to the browser console while the page loaded, for example “moment is not defined”.

Large scripts ship without source maps.

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

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 1,227 words of visible text.

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