dockingdrawer.com website review

18 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.

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

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

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

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

8 third-party services load with your homepage (Shopify, gotolstoy.com and convertflow.co and others), adding 4.0 MB and 528 ms of main-thread time.

Shopify costs a phone 151 ms of main-thread work and 3.2 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.

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

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

convertflow.co costs a phone 102 ms of main-thread work and 507 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.

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

About 52 KiB of CSS is downloaded but never applied on this page.

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

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 35.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Visit Canadian Storefront Find 🇨🇦 certified solutions des…”.

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

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

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

Real visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 947 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

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

Your homepage downloads 8.1 MB in 351 requests on a phone: images 3.1 MB (46), fonts 2.8 MB (49) and scripts 1.1 MB (99). Under 2 MB keeps phones on slow connections fast.

6 images are downloaded at several times the size a phone draws them, for example PointPods-PPCV815-3.jpg at 2,000 px wide, shown at 83 px. Resized copies would save about 603 KiB.

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

1 image (57 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

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

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

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

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

There are 2 <h1> headlines (“Hidden Power.” and “Hidden Power.”). One clear main headline is easier for people and search engines.

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 272 pages on dockingdrawer.com and 15 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.

/pages/clearance-deals and /collections/most-popular-vanity-solutions have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /pages/specification-resources, whose canonical is /collections/specification-resources. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/collections/all-products, /pages/specification-resources, /pages/content-buying-program, /collections/in-drawer-outlets, /collections/most-popular-charging-solutions and /products/fastest-charging-outlets and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

/collections/in-drawer-outlets and /products/most-usb-c-ports-outlets 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 117 found) and read each the way a search engine does.

6 errors were logged to the browser console while the page loaded, for example “Failed to execute 'observe' on 'MutationObserver': parameter 1 is not of type 'Node'.”.

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

1 link go through two or more redirects, for example https://www.dockingdrawer.com/pages/specification-resources.

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.

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

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.

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

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.

The homepage carries about 354 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

dockingdrawer.com has no SPF record, so mail servers can't tell which servers may send email as you. Your mail lands in spam more often, and anyone can send mail pretending to be you.

DMARC is set to p=none, so mail pretending to be dockingdrawer.com 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 Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 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.

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