xtetic.com website review

• Google's speed test didn't respond

  Google's speed test didn't respond for this site, so speed and Core Web Vitals are not measured here. Your full playbook measures them.

Not measured in this review.

• Page weight: 3.1 MB

  3.1 MB

  Your homepage downloads 3.1 MB on a phone, 429 KiB of it images (14%). Under 2 MB keeps phones on slow connections fast.

• An image on the first screen is lazy-loaded

  homepage-mobile-banner.webp 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 (2)

• 1 image in older formats

  1 image (43 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.

  Elements (1)

• About 0.9 g of CO₂ per visit

  0.88 g

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

• 8 text elements with low contrast

  8 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 (1 element)

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

  Elements (1)

• 1 image without alt text

  1 image has no alt text, which hurts accessibility and image search.

  Elements (1)

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

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

• 23 links without text

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

  Elements (3)

• 12 form fields without a label

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

  View source

• ARIA role should be appropriate for the element (14 elements)

  ARIA role should be appropriate for the element: 14 elements on the page fail this check, rated minor by axe-core.

  Elements (3)

• Headings skip levels

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

  View source

• Title is long (67 characters)

  Your title is 67 characters, so Google will cut it off around 60: “Top leading Aesthetics web for Professionals Aestheticians – XTETIC”.

  View source

• 145 internal links, 5 external

  The homepage links to 145 pages on xtetic.com and 5 external pages.

• Organization data is thin (3 of 6 facts)

  Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  View source

• 15 internal pages checked

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

• 6 small tap targets

  6 of 29 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_FAILED”.

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

  View source

• Thin social proof

  Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

• No analytics detected

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

• A 30-field form

  Your longest form asks for 30 fields (14 required). Every extra field lowers completion.

  View source

• No opening hours

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

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

  The homepage carries about 533 words of visible text.

• 5 trackers load before any consent

  5

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

• 16 cookies set on arrival

  16

  Opening the homepage sets 16 cookies, 1 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.

• 26 other companies contacted

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