about---blank.com website review

Not measured in this review.

• Tap response (INP) got 11% slower for real visitors

  +11%

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

• Largest content (LCP) held steady for real visitors

  -3%

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

• Page weight: 3.1 MB

  3.1 MB

  Your homepage downloads 3.1 MB on a phone, 549 KiB of it images (17%). Under 2 MB keeps phones on slow connections fast.

• 2 images below the first screen load straight away

  2 images further down the page (49 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  Elements (2)

• About 0.9 g of CO₂ per visit

  0.87 g

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

• 1 button without a name

  1 button has no accessible name, so screen readers announce just “button”.

  Elements (1)

• 35 text elements with low contrast

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

  Elements (3)

• Elements must only use permitted ARIA attributes (16 elements)

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

  Elements (3)

• All page content should be contained by landmarks (5 elements)

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

  Elements (3)

• Zoom is disabled

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

  Elements (1)

• 2 form fields without a label

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

  View source

• Headings skip levels

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

  View sourceElements (2)

• No structured data

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

• Open Graph partly set

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

  View source

• No X (Twitter) card tag

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

• 147 internal links, 4 external

  The homepage links to 147 pages on about---blank.com and 4 external pages.

• No Organization structured data

  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.

• 8 pages without a meta description

  /pages/puffers, /collections/shop-all, /collections/autumn-winter-26, /pages/monogram-cap, /collections/core-collection and /collections/headwear and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  Elements (8)

• 15 internal pages checked

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

• Short HSTS lifetime

  HSTS is set, but max-age is 91 days; one year is the recommended minimum.

• No Referrer-Policy

  No Referrer-Policy header, so full URLs can leak to the sites you link to.

• No Permissions-Policy

  No Permissions-Policy header to switch off camera, microphone and location for embedded content.

• Deprecated X-XSS-Protection

  X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

• No security.txt

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

• No CAA record

  about---blank.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.

• DNSSEC is off

  about---blank.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.

• No call to action on the first screen

  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 social proof

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

• No analytics detected

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

• No direct contact details

  No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

• No risk reducer

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

• About 585 words of copy

  The homepage carries about 585 words of visible text.

• DMARC is monitor-only (p=none)

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

• No DKIM key on the usual selectors

  We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

• Email authentication score: 60/100

  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.

• 7 trackers load before any consent

  7

  Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 mores (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.

• 27 cookies set on arrival

  27

  Opening the homepage sets 27 cookies (measured from a US location before any click).

• No consent tool detected

  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.

• 30 other companies contacted

  Loading the homepage contacts 30 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.