doitoutdoors.com website review

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

About 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

8 third-party services load with your homepage (Squarespace, Google CDN and sqspcdn.com and others), adding 4.9 MB and 949 ms of main-thread time.

8 images could be 539 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.

Your mobile performance score is 59 (desktop: 77). Pages that score under 90 lose visitors before the first paint.

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

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

Squarespace costs a phone 463 ms of main-thread work and 1.4 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.

Google CDN costs a phone 240 ms of main-thread work and 733 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.

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

sqspcdn.com costs a phone 108 ms of main-thread work and 789 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.

squarespace-cdn.com costs a phone 0 ms of main-thread work and 1.7 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.

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

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

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

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

Your largest element takes 6.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We do it outdoors daily, combining the big, bold presence o…”.

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

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

Scripts block taps and scrolling for 317 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.

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

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

Your homepage downloads 5.4 MB in 123 requests on a phone: scripts 2.9 MB (73), images 1.6 MB (14) and other files 363 KiB (10). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 14 characters: “do it outdoors”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“this is how we roll” and “this is how we roll this is how we roll”). One clear main headline is easier for people and search engines.

Structured data found (LocalBusiness, Organization and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/640a8c03278bc9668c1…”.

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

The homepage links to 71 pages on doitoutdoors.com and 19 external pages.

Your Organization JSON-LD is missing name, url, logo and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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.

/shadowfencing and /attribution-studies all use the title “Shadowfencing — do it outdoors”. Search engines can't tell which page to show for a search, so each competes with the others.

/shadowfencing and /attribution-studies use the same meta description. A description written for each page earns more clicks.

/multichannelmediaformats, /mobile-billboards and /faqs have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

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

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

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

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

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.

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