theanias.com website review

16 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.

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

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

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

8 third-party services load with your homepage (Shopify, ecomposer.app and nfcube.com and others), adding 1.2 MB and 354 ms of main-thread time.

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

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

Shopify costs a phone 256 ms of main-thread work and 912 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.

A phone's processor spends 3.0 s on main-thread work while loading, 879 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Polyfills for old browsers add 4 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

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

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

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

4 KiB could be saved by minifying CSS.

2 KiB could be saved by minifying JavaScript.

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

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

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

The first text or image appears after 2.1 s on a phone. Good is under 1.8 s.

Scripts block taps and scrolling for 202 ms in total while the page loads. Good is under 200 ms.

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.

Your homepage downloads 2.8 MB in 200 requests on a phone: scripts 1.0 MB (71), other files 802 KiB (77) and images 583 KiB (19). Under 2 MB keeps phones on slow connections fast.

ba177-2.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).

8 images (416 KiB) are 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.

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

1 button has no accessible name, so screen readers announce just “button”.

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

5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

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

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

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

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

Your title is only 5 characters: “Anias”. 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.

The homepage links to 112 pages on theanias.com and 10 external pages.

There is no https://www.theanias.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://www.theanias.com/pages/contact-us has no meta description, so Google writes the search snippet from whatever text it finds.

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

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

5 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading '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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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

The homepage carries about 723 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

Opening the homepage sets 6 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 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.