docos.us website review

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

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

12 images could be 546 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

5 third-party services load with your homepage (Shopify, shop.app and Google Fonts and others), adding 1.1 MB and 70 ms of main-thread time.

Shopify costs a phone 65 ms of main-thread work and 1,011 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.

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

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

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

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

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

Polyfills for old browsers add 17 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.

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

Your largest element takes 3.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Docos lighting glowing in a warm evening interior for Black…”.

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

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

Your homepage downloads 2.5 MB in 240 requests on a phone: scripts 797 KiB (106), other files 740 KiB (97) and images 709 KiB (15). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example 2026_Black_Friday_1016__4.jpg at 1,024 px wide, shown at 166 px. Resized copies would save about 48 KiB.

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

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

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

Elements with visible text labels do not have matching accessible names. (3 elements).

Your title is 70 characters, so Google will cut it off around 60: “Designer Lighting for Every Room | Pendant, Wall & Table Lamps | Docos”.

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

Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: potentialAction.target is not an absolute URL ("/search?q={search_term_string}")”.

12 links have no real href, so search engines can't follow them.

The homepage links to 217 pages on docos.us and 10 external pages.

/collections/all-collections has no <h1> headline, so visitors and search engines get no clear main topic.

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

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.

docos.us 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.

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.

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

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.

The homepage carries about 1,173 words of visible text.

DMARC is set to p=none, so mail pretending to be docos.us is still delivered. Reports are on, so moving to quarantine is the next step.

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 Klaviyo 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 4 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.