chigee.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: 228 ms

  228 ms

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

• Real-user FCP: 2.0 s

  2.0 s

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

• Real-user TTFB: 982 ms

  982 ms

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

• Page weight: 5.0 MB

  5.0 MB

  Your homepage downloads 5.0 MB on a phone, 564 KiB of it images (11%). Under 2 MB keeps phones on slow connections fast.

• An image on the first screen is lazy-loaded

  Snipaste_2025-02-18_15-00-38.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)

• 3 images below the first screen load straight away

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

  Elements (3)

• About 1.4 g of CO₂ per visit

  1.41 g

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

• ARIA attributes must conform to valid values (1 element)

  ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

  Elements (1)

• 9 tap targets too small

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

  Elements (3)

• 1 text element with low contrast

  1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  Elements (1)

• Scrollable region must have keyboard access (1 element)

  Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  Elements (1)

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

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

  Elements (2)

• Zoom is disabled

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

  Elements (1)

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

• 212 internal links, 17 external

  The homepage links to 212 pages on chigee.com and 17 external pages.

• 15 pages without an H1

  /pages/comparison, /products/aio-6, /products/sr1, /products/aio-6-lte, /products/aio5-play-for-bmw and /products/aio-5play and 9 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 70 found) and read each the way a search engine does.

• 6 small tap targets

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

• 6 JavaScript errors while loading

  6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

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

• DNSSEC is off

  chigee.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 direct contact details

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

• About 440 words of copy

  The homepage carries about 440 words of visible text.

• No DMARC policy

  chigee.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

• 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: 35/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 (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.

• 42 other companies contacted

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