shub.coffee website review

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

About 436 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.

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

Your mobile performance score is 31. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

8 third-party services load with your homepage (salla.network, Google Tag Manager and Facebook and others), adding 7.6 MB and 1.9 s of main-thread time.

salla.network costs a phone 981 ms of main-thread work and 6.6 MB 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.

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

Google Tag Manager costs a phone 392 ms of main-thread work and 528 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.

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

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

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

5 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 22 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 37.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “سبيشلتي هاب image-slider-0”.

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

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

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

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

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

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

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

Your homepage downloads 11.9 MB in 355 requests on a phone: images 6.5 MB (172), other files 3.3 MB (85) and scripts 1.6 MB (84). Under 2 MB keeps phones on slow connections fast.

466b57f7-9b55-4ddd-924e-6dff830c2588-original.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).

6 images are downloaded at several times the size a phone draws them, for example 466b57f7-9b55-4ddd-924e-6dff830c2588-original.webp at 1,440 px wide, shown at 390 px. Resized copies would save about 226 KiB.

3 images (119 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.

4 images further down the page (184 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 3.37 g of CO₂e: 404.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

1 dropdown has no label.

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

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

Alternative text of images should not be repeated as text: 5 elements on the page fail this check, rated minor by axe-core.

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

Elements with visible text labels do not have matching accessible names. (4 elements).

Your title is only 11 characters: “سبيشلتي هاب”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

The homepage links to 79 pages on shub.coffee and 2 external pages.

https://shub.coffee/ar/xbloom-studio-machines/c1323405371 and https://shub.coffee/en/-/c1323405371 all use the title “xBloom Studio Machines | سبيشلتي هاب”. Search engines can't tell which page to show for a search, so each competes with the others.

Your homepage links to 14 pages by a URL that isn't their canonical one, for example https://shub.coffee/en/-/brand-1905788328, whose canonical is https://shub.coffee/en/brim/brand-1905788328. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://shub.coffee/en/-/brand-1905788328, https://shub.coffee/en/-/brand-332939014, https://shub.coffee/en/-/brand-1450552784 and https://shub.coffee/en/-/c1323405371 use the same meta description. A description written for each page earns more clicks.

https://shub.coffee/ar/xbloom-studio-machines/c1323405371, https://shub.coffee/en/-/brand-1905788328, https://shub.coffee/en/-/brand-496591093, https://shub.coffee/en/-/brand-1802972050, https://shub.coffee/en/-/brand-157850625 and https://shub.coffee/en/-/brand-2046949215 and 9 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://shub.coffee/en/-/brand-604636138 and https://shub.coffee/en/-/brand-1074490935 took over 3 s to send their HTML from our server.

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

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

Chrome logged issues while loading the page (“Cookie”).

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.

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

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

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