dyper.com website review

Not measured in this review.

• Fails Core Web Vitals for real visitors

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

• Real-user INP: 230 ms

  230 ms

  Real visitors wait 230 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

• Tap response (INP) held steady for real visitors

  +7%

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

• Page weight: 5.6 MB

  5.6 MB

  Your homepage downloads 5.6 MB on a phone, 223 KiB of it images (4%). Under 2 MB keeps phones on slow connections fast.

• An image on the first screen is lazy-loaded

  dyper_-_slide_2_-_Mob.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  Elements (1)

• 2 images in older formats

  2 images (111 KiB) are 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.

  Elements (2)

• About 1.6 g of CO₂ per visit

  1.60 g

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

• Images must have alternative text (1 element)

  Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

  Elements (1)

• 14 text elements with low contrast

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

  Elements (3)

• 7 tap targets too small

  7 tap targets are too small or too close together to hit reliably with a finger.

  Elements (3)

• Scrollable region must have keyboard access (2 elements)

  Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

  Elements (2)

• Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

  Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  Elements (1)

• Zoom is disabled

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

  Elements (1)

• All page content should be contained by landmarks (1 element)

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

  Elements (1)

• 2 links without text

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

  Elements (2)

• Alternative text of images should not be repeated as text (1 element)

  Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

  Elements (1)

• 56 internal links, 10 external

  The homepage links to 56 pages on dyper.com and 10 external pages.

• 1 linked page is broken

  Your homepage links to /faqs, which answers with an error. Visitors hit a dead end and search engines drop it.

  Elements (1)

• 6 pages without a meta description

  /products/redyper-pickups, /pages/contact, /collections/all, /pages/loyalty-program, /pages/about-us and /blogs/news have no meta description, so Google writes the search snippet from whatever text it finds.

  Elements (6)

• 4 pages without an H1

  /products/redyper-pickups, /collections/shop-all, /pages/contact and /pages/about-us have no <h1> headline, so visitors and search engines get no clear main topic.

• 15 internal pages checked

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

• 11 small tap targets

  11 of 18 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

• 2 JavaScript errors while loading

  2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

• 1 broken link to your own pages

  1 link from your homepage to your own site is broken, for example https://dyper.com/faqs (404).

• 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

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

  dyper.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 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 880 words of copy

  The homepage carries about 880 words of visible text.

• DMARC is monitor-only (p=none)

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

• Email authentication score: 70/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.

• 12 trackers load before any consent

  12

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

• 25 cookies set on arrival

  25

  Opening the homepage sets 25 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.

• 55 other companies contacted

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