Website review, no card needed

xeoxarel.com logo

xeoxarel.com website review

Visit site (opens in a new tab)Reviewed 10 November 202628 issues · 67 checks

This review found 28 issues worth fixing on xeoxarel.com, 6 of them high impact, across 67 checks. The most urgent: 3,502 HTML elements. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of xeoxarel.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. xeoxarel.com at 0.7 s0.7 s
  2. xeoxarel.com at 1.4 s1.4 s
  3. xeoxarel.com at 2.0 s2.0 s
  4. xeoxarel.com at 2.7 s2.7 s
  5. xeoxarel.com at 3.4 s3.4 s
  6. xeoxarel.com at 4.1 s4.1 s
  7. xeoxarel.com at 4.8 s4.8 s
  8. xeoxarel.com at 5.4 s5.4 s

Speed

6 to fix81
  • 3,502 HTML elements

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

  • Mobile performance score: 81

    81/100

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

  • Improve image delivery

    350 ms · 428 KiB

    4 images could be 428 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

  • Render-blocking requests

    750 ms

    4 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.

  • Reduce unused CSS

    300 ms · 50 KiB

    About 50 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Hexton adds 94 ms

    94 ms

    Hexton costs a phone 94 ms of main-thread work and 466 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.

  • Use efficient cache lifetimes

    186 KiB

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Hexton, jQuery CDN and Shopify), adding 504 KiB and 120 ms of main-thread time.

  • Reduce unused JavaScript

    163 KiB

    About 163 KiB of JavaScript is downloaded but never used on this page.

  • 3 long tasks on the main thread

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

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 checks passed
  • Main-thread work: 1.2 s

    A phone's processor spends 1.2 s on main-thread work while loading, 352 ms of it running JavaScript. That is comfortably low.

  • Server response: 11 ms

    11 ms

    Your server sent the HTML in 11 ms, well inside Google's 600 ms guideline.

Core Web Vitals

3 to fix79
  • Largest Contentful Paint: 4.5 s

    4.5 s

    Your largest element takes 4.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Speed Index: 4.7 s

    4.7 s

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

  • Time to Interactive: 5.6 s

    5.6 s

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

3 checks passed
  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.027

    0.027

    The layout barely moves while loading (CLS 0.027, good is under 0.1).

  • Total Blocking Time: 21 ms

    21 ms

    Scripts block the page for only 21 ms while loading. Good is under 200 ms.

Images and page weight

3 to fix68
  • Page weight: 2.4 MB in 167 requests

    2.4 MB

    Your homepage downloads 2.4 MB in 167 requests on a phone: other files 778 KiB (92), images 724 KiB (6) and scripts 695 KiB (61). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    272 KiB

    2 images are downloaded at several times the size a phone draws them, for example 1_d3ca7d76-3f07-480e-b0a7-7024e0348c13.jpg at 3,229 px wide, shown at 390 px. Resized copies would save about 272 KiB.

  • 2 images below the first screen load straight away

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

  • About 0.7 g of CO₂ per visit

    0.67 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

4 to fixGoogle 8894
  • Hidden but focusable

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

  • 1 image without alt text

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

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

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

  • 7 links without text

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

  • Headings skip levels

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

1 checks passed
  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9280
  • Title is long (66 characters)

    Your title is 66 characters, so Google will cut it off around 60: “Xeoxarel -Professional Women's vests designer! – Xeoxarel Official”.

  • Meta description is short (58 characters)

    Your meta description is only 58 characters: “Xeoxarel Womens vests-Professional Women's vests designer.”. 70 to 160 characters is enough to sell the click.

  • 2 H1 headlines

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 33 internal links, 1 external

    The homepage links to 33 pages on xeoxarel.com and 1 external page.

4 checks passed
  • Canonical URL set

    The canonical URL is https://xeoxarel.com/.

  • Structured data in place

    Structured data found: Organization.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://xeoxarel.com/sitemap.xml.

AI search readiness

1 to fix83
  • 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.

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • llms.txt published

    The site publishes https://xeoxarel.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 13 pages without a meta description

    https://xeoxarel.com/collections/all, https://xeoxarel.com/pages/about-xeoxarel, https://xeoxarel.com/pages/contact-us, https://xeoxarel.com/collections/2, https://xeoxarel.com/collections/sleeves-1 and https://xeoxarel.com/collections/vest and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://xeoxarel.com/collections/all, https://xeoxarel.com/collections, https://xeoxarel.com/pages/about-xeoxarel, https://xeoxarel.com/pages/warranty, https://xeoxarel.com/pages/contact-us and https://xeoxarel.com/collections/2 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 17 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

Google 100100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    10 of 11 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix50
  • 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 social proof

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

  • No analytics detected

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

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

  • Only about 90 words

    The homepage has only about 90 words of visible text; thin pages give Google and first-time buyers little to go on.

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

2 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact Us”, “Shop Now” and “Contact information”.

  • 4 short forms

    4 short forms (1 field at most) are right on the homepage.

Privacy and tracking

  • 8 cookies set on arrival

    8

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

  • 8 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at xeoxarel.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 1 app. It is code from another company running for your shoppers.

Apps your storefront loads

hextom.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on xeoxarel.com, including 9 speed issues, 4 SEO issues and 5 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25