noorio.com website review

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

8 third-party services load with your homepage (YouTube, Google Tag Manager and TikTok and others), adding 2.9 MB and 1.1 s of main-thread time.

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

About 1.1 MB of JavaScript is downloaded but never used on this page.

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

YouTube costs a phone 347 ms of main-thread work and 993 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.

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

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

TikTok costs a phone 138 ms of main-thread work and 295 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 1,593 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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

Polyfills for old browsers add 33 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.

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

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

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.

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

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

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

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

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

Your homepage downloads 5.4 MB in 284 requests on a phone: scripts 2.4 MB (73), images 2.0 MB (65) and other files 696 KiB (118). Under 2 MB keeps phones on slow connections fast.

3_8eeade98-717e-4967-84b0-c1149bca2d92.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).

3 images are downloaded at several times the size a phone draws them, for example hub01_1500x1901.jpg at 1,500 px wide, shown at 366 px. Resized copies would save about 284 KiB.

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

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

Interactive controls must not be nested: 5 elements on the page fail this check, rated serious by axe-core.

Scrollable region must have keyboard access: 3 elements on the page fail 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.

1 visible link has no text or label, so screen readers cannot say where it goes.

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

Elements with visible text labels do not have matching accessible names. (1 element).

There are 20 <h1> headlines (“”, “Solar Camera Set” and “Bestseller”). One clear main headline is easier for people and search engines.

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

5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

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

The homepage links to 144 pages on noorio.com and 35 external pages.

https://noorio.com/collections/all, https://noorio.com/pages/holiday, https://noorio.com/pages/noorio-cloud-storage and https://noorio.com/blogs/news have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=343040918&Ver=2&mid=3aeb1b79-49e0-48b3-9a3e-e0dcc03bd597&bo=1&sid=623f0290da4b11f194b997740a2ef603&vid=623f2820da4b11f1acbae534d6ad01c3&vids=1&msclkid=N&pi=918639831&l.

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

21 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

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.

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.

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

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