weareshadow.com website review

website-files.com costs a phone 1.3 s of main-thread work and 14.4 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

8 files are served with short cache lifetimes, so returning visitors download them again (13.5 MB).

7 third-party services load with your homepage (website-files.com, Clarity and Google Tag Manager and others), adding 14.7 MB and 1.6 s of main-thread time.

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

About 273 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

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

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

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

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

13 KiB could be saved by minifying JavaScript.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

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

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

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

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

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

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 14.9 MB in 64 requests on a phone: media 13.4 MB (4), images 620 KiB (15) and scripts 609 KiB (14). Under 2 MB keeps phones on slow connections fast.

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

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

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

3 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

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

There are 12 <h1> headlines (“Creative Strategy”, “Creative Strategy” and “Media Relations”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

Your meta description is 214 characters; Google truncates after about 160, so the end of your pitch is cut.

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

The homepage links to 69 pages on weareshadow.com and 39 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 https://www.weareshadow.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://www.weareshadow.com/feed/shadow-creates-the-first-spaceship-going-to-mars, https://www.weareshadow.com/feed/ipsum-doirum-lorem-oliuyrm, https://www.weareshadow.com/feed/lorem-ipsum-dolor-set-orium-ipsum and https://www.weareshadow.com/feed/shadow-partners-with-elf-to-lorem-ipsum-dolor all use the title “SHADOW”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.weareshadow.com/projects/major-moisture-matchup, https://www.weareshadow.com/projects/feel-whats-possible, https://www.weareshadow.com/projects/bottle-service, https://www.weareshadow.com/projects/judge-beauty, https://www.weareshadow.com/projects/spring-try-guide and https://www.weareshadow.com/projects/pat-mcgrath-labs-x-shop-with-google and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.weareshadow.com/projects/major-moisture-matchup, https://www.weareshadow.com/projects/feel-whats-possible, https://www.weareshadow.com/projects/bottle-service, https://www.weareshadow.com/projects/judge-beauty, https://www.weareshadow.com/projects/spring-try-guide and https://www.weareshadow.com/projects/pat-mcgrath-labs-x-shop-with-google and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.weareshadow.com/feed/shadow-creates-the-first-spaceship-going-to-mars, https://www.weareshadow.com/feed/lorem-ipsum-dolor-set-orium-ipsum and https://www.weareshadow.com/feed/shadow-partners-with-elf-to-lorem-ipsum-dolor 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 13 pages linked from your homepage and read each the way a search engine does.

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

Large scripts ship without source maps.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 47 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage has only about 158 words of visible text; thin pages give Google and first-time buyers little to go on.

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.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Microsoft Clarity (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 5 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.