custype.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 LCP: 2.8 s

  2.8 s

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

• Real-user CLS: 0.17

  0.17

  For real visitors the layout shifts by 0.17 (75th percentile). Good is under 0.1.

• Real-user FCP: 2.5 s

  2.5 s

  Real visitors see the first content after 2.5 s (75th percentile). Good is under 1.8 s.

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

  +13%

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

• Largest content (LCP) held steady for real visitors

  0%

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

• Page weight: 4.5 MB

  4.5 MB

  Your homepage downloads 4.5 MB on a phone, 1.3 MB of it images (28%). Under 2 MB keeps phones on slow connections fast.

• An image on the first screen is lazy-loaded

  3_0cf34492-9bf4-4057-8425-03bce7836917.jpg 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 (3)

• 1 image far larger than shown

  25 KiB

  1 image is downloaded at several times the size a phone draws it, for example christmas_phone_case_with_adjustable_crossbody_strap.jpg at 1,367 px wide, shown at 390 px. Resized copies would save about 25 KiB.

  Elements (1)

• 2 images below the first screen load straight away

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

  Elements (2)

• About 1.3 g of CO₂ per visit

  1.29 g

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

• Hidden but focusable

  4 elements hidden from screen readers can still receive keyboard focus.

  Elements (3)

• 2 tap targets too small

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

  Elements (2)

• 16 images without alt text

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

  View sourceElements (3)

• 134 links without text

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

  Elements (3)

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

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

  Elements (2)

• Page should contain a level-one heading (1 element)

  Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  Elements (1)

• 17 form fields without a label

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

  View source

• No H1 headline

  There is no <h1>, so neither visitors nor Google get a clear main headline.

• Title is long (70 characters)

  Your title is 70 characters, so Google will cut it off around 60: “Custype Crossbody Phone Cases for iPhone & Samsung with wallet & strap”.

  View source

• Meta description is long (220 characters)

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

  View source

• Structured data has 1 problem

  Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("https:files/20211214-170603.png")”.

• 542 internal links, 6 external

  The homepage links to 542 pages on custype.com and 6 external pages.

• 12 pages without an H1

  /pages/christmas-lookbook, /collections/crossbody-phone-case, /collections/iphone-18-series-cases, /collections/custype-annual-promotion, /pages/personalized-phone-cases-diy and /collections/iphone-18-pro-max-cases and 6 others 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 116 found) and read each the way a search engine does.

• 23 small tap targets

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

• 4 JavaScript errors while loading

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

• 4 broken links to your own pages

  4 links from your homepage to your own site are broken, for example https://custype.com/collections/iphone-17-air-case (500).

• 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

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

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

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

• Local business without LocalBusiness data

  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 phone number on the homepage

  A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

• 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 opening hours

  The homepage shows no opening hours. If customers visit or call, show when.

• No map or directions link

  There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

• 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 526 words of copy

  The homepage carries about 526 words of visible text.

• DMARC is monitor-only (p=none)

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

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

• 6 trackers load before any consent

  6

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

• 20 cookies set on arrival

  20

  Opening the homepage sets 20 cookies, 2 of them by other companies (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.

• 31 other companies contacted

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