3chub.com website review

6 third-party services load with your homepage (loloyal.com, Google Tag Manager and Facebook and others), adding 1.0 MB and 993 ms of main-thread time.

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

Your mobile performance score is 70 (desktop: 82). Pages that score under 90 lose visitors before the first paint.

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

loloyal.com costs a phone 348 ms of main-thread work and 390 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.

Google Tag Manager costs a phone 308 ms of main-thread work and 298 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.1 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Facebook costs a phone 278 ms of main-thread work and 222 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.

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

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

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

89 KiB JavaScript is shipped twice across bundles.

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

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 2.7 MB in 209 requests on a phone: scripts 1.1 MB (49), other files 792 KiB (102) and images 739 KiB (33). Under 2 MB keeps phones on slow connections fast.

1_bbff55c2-a0d6-4b5b-9898-d296b77c7a15.jpg 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 (352 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.77 g of CO₂e: 92.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Links must have discernible text: 10 elements on the page fail this check, rated serious by axe-core.

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

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

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

Your title is 70 characters, so Google will cut it off around 60: “Best Price in 3CHUB |Mobile phones|Accessories|Home appliances – 3chub”.

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

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

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.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

Your <h1> is empty.

The homepage links to 315 pages on 3chub.com and 7 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.

/collections/vivo and /collections/honor have no meta description, so Google writes the search snippet from whatever text it finds.

/collections/itel-mobile-phone and /collections/xiaomi-mobile-phone use the same meta description. A description written for each page earns more clicks.

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

22 of 50 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”.

2 links from your homepage to your own site are broken, for example https://www.3chub.com/collections/infinix-note-series (404).

1 link to other sites is dead, for example https://www.linkedin.com/in/3chub-brand-b511a61a3/ (999).

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

3chub.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

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.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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.

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

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

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Meta Pixel (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 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 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.