dixast.com website review

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

About 117 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

About 45 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.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 300 ms.

Google Fonts costs a phone 0 ms of main-thread work and 351 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.

41 KiB could be saved by minifying JavaScript.

4 third-party services load with your homepage (sealsubscriptions.com, Shopify and shop.app and others), adding 493 KiB and 38 ms of main-thread time.

2 images could be 11 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

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

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.

IMAGE_8.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).

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

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.

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

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 6 characters: “Dixast”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

Your <h1> is empty.

The homepage links to 34 pages on dixast.com and 1 external page.

https://dixast.com/collections/all-products, https://dixast.com/pages/contact, https://dixast.com/products/supplement-needs-female-pcos-240-capsules, https://dixast.com/products/supplement-needs-gut-guard-240-capsules, https://dixast.com/products/supplement-needs-purcaf-l-theanine-60-capsules and https://dixast.com/products/supplement-needs-female-fertility-90-capsules and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://dixast.com/products/supplement-needs-purcaf-l-theanine-60-capsules%E2%84%A2, whose canonical is https://dixast.com/products/supplement-needs-purcaf-l-theanine-60-capsules%e2%84%a2. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://dixast.com/pages/contact, https://dixast.com/pages/female and https://dixast.com/pages/performance-needs have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

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

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

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

The homepage carries about 815 words of visible text.

Opening the homepage sets 5 cookies (measured from a US location before any click).

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.

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