neubergdiagnostics.com website review

The page goes through 2 redirects before it starts loading, costing about 173.0 s. Link and advertise the final URL directly.

About 11.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 80.8 s faster on a phone.

132 files are served with short cache lifetimes, so returning visitors download them again (15.0 MB).

YouTube costs a phone 5.9 s of main-thread work and 18.4 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

About 142 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 3.5 s faster on a phone.

Google Tag Manager costs a phone 1.5 s of main-thread work and 1.6 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

8 third-party services load with your homepage (YouTube, Google Tag Manager and Other Google APIs/SDKs and others), adding 21.6 MB and 7.8 s of main-thread time.

31 images could be 7.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

razorpay.com costs a phone 107 ms of main-thread work and 810 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.

Other Google APIs/SDKs costs a phone 125 ms of main-thread work and 318 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.

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

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

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.

For real visitors the layout shifts by 0.78 (75th percentile). Good is under 0.1.

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

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 54.7 MB in 1,005 requests on a phone: scripts 26.3 MB (248), images 18.9 MB (242) and other files 4.2 MB (339). Under 2 MB keeps phones on slow connections fast.

2 images weigh 3.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 1784888840345-Mobile banner-03.jpg at 5,084 px wide, shown at 295 px. Resized copies would save about 3.5 MB.

10 images further down the page (2.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

8 images (1.8 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 15.50 g of CO₂e: 1860.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Images must have alternative text: 7 elements on the page fail this check, rated critical by axe-core.

55 elements hidden from screen readers can still receive keyboard focus.

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

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

4 frames have no title, so screen-reader users cannot tell what they contain.

Heading levels should only increase by one: 3 elements on the page fail this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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.

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

There is no robots.txt at neubergdiagnostics.com/robots.txt, the first file search crawlers ask for.

The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

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

A phone browser shows 2,915 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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.

There is no https://www.neubergdiagnostics.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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

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

5 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://www.neubergdiagnostics.com/src/styles/Common.module.css' because its MIME type ('t…”.

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

Large scripts ship without source maps.

Requests the geolocation permission on page load.

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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.

There is no form on the homepage, so every lead has to click through to another page first.

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

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