178degrees.com website review

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

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

16 images could be 2.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

8 third-party services load with your homepage (Google Tag Manager, Bigcommerce and Facebook and others), adding 7.0 MB and 740 ms of main-thread time.

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

Bigcommerce costs a phone 204 ms of main-thread work and 6.0 MB 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.

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

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

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

About 41 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.

29 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

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.

5 KiB could be saved by minifying JavaScript.

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

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

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

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

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.

Your homepage downloads 7.0 MB in 66 requests on a phone: images 5.7 MB (24), scripts 1.1 MB (21) and fonts 153 KiB (4). Under 2 MB keeps phones on slow connections fast.

3 images are downloaded at several times the size a phone draws them, for example slide4.jpg at 1,267 px wide, shown at 390 px. Resized copies would save about 271 KiB.

1 image further down the page (20 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 1.99 g of CO₂e: 238.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

7 tap targets are too small or too close together to hit reliably with a finger.

1 element hidden from screen readers can still receive keyboard focus.

1 link inside paragraphs relies on colour alone to stand out.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

Your title is only 11 characters: “178 Degrees”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

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

Your <h1> is empty.

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

The homepage links to 68 pages on 178degrees.com and 4 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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

/shop-all/patagonian-msc-certified-toothfish-fillet-2-2-2-3kg-chilean-seabass and /shop-all/patagonian-toothfish-steak-cut-300g-chilean-seabass all use the title “Patagonian South Georgia Seafoods MSC Certified toothfish fillet stea…”. Search engines can't tell which page to show for a search, so each competes with the others.

/products, /pork, /lamb, /dessert, /seafood and /meats and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

/products, /pork, /lamb, /dessert, /seafood and /meats and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

/lamb, /chilled-meats, /plant-based and /pantry 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 15 pages linked from your homepage (of 37 found) and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

HSTS is set, but max-age is 0 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.

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

178degrees.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.

178degrees.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.

Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

DMARC is set to p=none, so mail pretending to be 178degrees.com is still delivered. Add a report address, check the reports, then move to quarantine.

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