nikshanonline.com website review

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Google CDN and Hotjar and others), adding 2.4 MB and 2.2 s of main-thread time.

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

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

Google CDN costs a phone 506 ms of main-thread work and 739 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.

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

Hotjar costs a phone 262 ms of main-thread work and 231 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 long tasks block the main thread while loading, the longest for 253 ms. During a long task the page ignores taps.

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

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

Desktop scores 62 but mobile only 36. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

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

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

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 4.6 MB in 348 requests on a phone: scripts 2.8 MB (103), images 918 KiB (31) and other files 367 KiB (26). Under 2 MB keeps phones on slow connections fast.

3 images weigh 2.7 MB together. On a phone connection a single image that size takes seconds.

4 images are downloaded at several times the size a phone draws them, for example VU-LED-85-INCHES-85TV-1.png at 1,000 px wide, shown at 155 px. Resized copies would save about 1.5 MB.

8 images (3.1 MB) 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 1.31 g of CO₂e: 157.8 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.

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

1 element hidden from screen readers can still receive keyboard focus.

28 images have no alt text, which hurts accessibility and image search.

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.

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

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

The homepage links to 660 pages on nikshanonline.com and 26 external pages.

robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example /product-category/mobiles-gadgets/audio, whose canonical is /product-category/mobiles-and-gadgets-online/audio. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/product-category/mobiles-gadgets/audio and /product-category/tv-displays took over 3 s to send their HTML from our server.

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

10 images failed to load on a phone, for example https://nikshanonline.com/wp-content/themes/woodmart/images/lazy.svg.

5 images are served at too low a resolution for sharp phone screens.

1 link from your homepage to your own site is broken, for example https://nikshanonline.com/cdn-cgi/content?id=.s8liwotKe9Is5NCqOwOwYprk82CDkZhS5M1KA660Qs-1792667497.0474434-1.2.1.1-Lihn9XFg3QeI8KkLckXGxDnad_u83rduz.4CkHoJhsb2TEorxg2_AY0UlRFOFltk (404).

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

5 links go through two or more redirects, for example https://nikshanonline.com/product-category/cooling-solutions/.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

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.

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

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

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.

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,298 words of visible text.

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

nikshanonline.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

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 Ads, Google Analytics, Google Tag Manager, Hotjar and LinkedIn Insight 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 21 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 30 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.