gorillashed.com website review

10 images could be 361 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.3 s faster on a phone.

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

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

4 third-party services load with your homepage (Klaviyo, Shopify and shop.app and others), adding 428 KiB and 174 ms of main-thread time.

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

About 74 KiB of JavaScript is downloaded but never used on this page.

1 long task block the main thread while loading, the longest for 58 ms. During a long task the page ignores taps.

Polyfills for old browsers add 25 KiB JavaScript that modern phones do not need.

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.

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

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

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

1 image 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 71 ms to 77 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.9 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Gorilla-icon-reveal-min.gif weighs 611 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 2.6 MB in 228 requests on a phone: images 833 KiB (19), other files 833 KiB (103) and scripts 503 KiB (70). Under 2 MB keeps phones on slow connections fast.

1 image (611 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.

1 image further down the page (611 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

ARIA dialog and alertdialog nodes should have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

1 image has no alt text, which hurts accessibility and image search.

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

There are 2 <h1> headlines (“Gorilla Sheds” and “STRENGTH LIKE NO OTHER.”). One clear main headline is easier for people and search engines.

Structured data found (Organization, WebPage and WebSite) but with 1 problem, for example “ld+json block 3 is not valid JSON (Expected ',' or '}' after property value in JSON at position)”.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 82 pages on gorillashed.com and 7 external pages.

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

15 of 45 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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.

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

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach 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 320 words of visible text.

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 Klaviyo (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 10 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.