ajlfashion.com website review

13 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 950 ms faster on a phone.

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

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

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

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

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

1 long task block the main thread while loading, the longest for 247 ms. During a long task the page ignores taps.

6 third-party services load with your homepage (Shopify, conversionbear.com and sweethelp.io and others), adding 535 KiB and 181 ms of main-thread time.

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

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

About 10 KiB of CSS is downloaded but never applied on this page.

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

4 KiB could be saved by minifying JavaScript.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

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

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

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

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

For real visitors the layout shifts by 0.11 (75th percentile). Good is under 0.1.

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

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

The layout shifts by 0.122 while loading, so content jumps under the reader's thumb. Good is under 0.1.

15 images have no width and height attributes, so the layout jumps as each one loads.

Your homepage downloads 3.6 MB in 306 requests on a phone: images 1.7 MB (18), other files 1.1 MB (171) and scripts 465 KiB (72). Under 2 MB keeps phones on slow connections fast.

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

By the Sustainable Web Design model, a visit to your homepage emits about 1.02 g of CO₂e: 121.9 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”.

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

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

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

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

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Your meta description is 320 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (Organization and WebSite) but with 2 problems, for example “Organization: sameAs is not an absolute URL ("x.com/ayodelejaynelag")”.

Your <h1> is empty.

The homepage links to 75 pages on ajlfashion.com and 13 external pages.

Your homepage links to https://ajlfashion.com/x.com/ayodelejaynelag and https://ajlfashion.com/tiktok.com/@ayodelejaynelagos, which answer with an error. Visitors hit a dead end and search engines drop them.

Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://ajlfashion.com/en-us/collections/new-in-latest-trends/products/motif-scarf, whose canonical is https://ajlfashion.com/en-us/products/motif-scarf. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 123 testimonial or review blocks. 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.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 1,017 words of visible text.

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

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