selectomobiles.com website review

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

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

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

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

38 KiB could be saved by minifying JavaScript.

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

2 long tasks block the main thread while loading, the longest for 68 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).

1 image could be 23 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

3 third-party services load with your homepage (Shopify, Bootstrap CDN and Google Fonts), adding 173 KiB and 6 ms of main-thread time.

Polyfills for old browsers add 6 KiB JavaScript that modern phones do not need.

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.

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.

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

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

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

Real visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 140 ms to 162 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 3.1 s to 3.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.1 MB in 195 requests on a phone: images 887 KiB (76), other files 720 KiB (71) and scripts 287 KiB (34). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example Banner102_7e876926-115c-4517-a9ba-902adc3e0d83_1920x.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 92 KiB.

2 images further down the page (73 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 0.61 g of CO₂e: 72.7 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”.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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.

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

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

60 links have no real href, so search engines can't follow them.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is only 59 characters: “Selecto Mobiles is Your one stop mobiles & accessories shop”. 70 to 160 characters is enough to sell the click.

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

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 218 pages on selectomobiles.com and 14 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://selectomobiles.com/collections/all-mobiles, https://selectomobiles.com/collections/3gb-above-ram and https://selectomobiles.com/collections/upcoming-mobiles have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 11 pages by a URL that isn't their canonical one, for example https://selectomobiles.com/collections/apple-iphone/products/apple-iphone-11-pro, whose canonical is https://selectomobiles.com/products/apple-iphone-11-pro. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://selectomobiles.com/collections/all-mobiles, https://selectomobiles.com/collections/3gb-above-ram, https://selectomobiles.com/collections/upcoming-mobiles and https://selectomobiles.com/collections have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

1 image is served at too low a resolution for sharp phone screens.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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 has only about 215 words of visible text; thin pages give Google and first-time buyers little to go on.

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.

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

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