blallab.com website review

Not measured in this review.

• Fails Core Web Vitals for real visitors

  Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

• Real-user LCP: 2.5 s

  2.5 s

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

• Real-user INP: 211 ms

  211 ms

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

• Real-user FCP: 1.8 s

  1.8 s

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

• Real-user TTFB: 908 ms

  908 ms

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

• Tap response (INP) held steady for real visitors

  +3%

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

• Page weight: 5.5 MB

  5.5 MB

  Your homepage downloads 5.5 MB on a phone, 4.3 MB of it images (79%). Under 2 MB keeps phones on slow connections fast.

• 2 images over 500 KB

  2 images weigh 3.1 MB together. On a phone connection a single image that size takes seconds.

  Elements (2)

• 3 images far larger than shown

  1.1 MB

  3 images are downloaded at several times the size a phone draws them, for example herobanner1.png at 1,536 px wide, shown at 390 px. Resized copies would save about 1.1 MB.

  Elements (3)

• 6 images in older formats

  6 images (4.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.

  Elements (5)

• An image on the first screen is lazy-loaded

  herobanner1.png 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).

  Elements (1)

• 2 images below the first screen load straight away

  2 images further down the page (441 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  Elements (2)

• About 1.6 g of CO₂ per visit

  1.56 g

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

• 2 buttons without a name

  2 buttons have no accessible name, so screen readers announce just “button”.

  Elements (2)

• 12 text elements with low contrast

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

  Elements (3)

• All page content should be contained by landmarks (19 elements)

  All page content should be contained by landmarks: 19 elements on the page fail this check, rated moderate by axe-core.

  Elements (3)

• 1 form field without a label

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

  View sourceElements (1)

• 1 link without text

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

  Elements (1)

• Headings skip levels

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

  View sourceElements (2)

• 34 internal links, 15 external

  The homepage links to 34 pages on blallab.com and 15 external pages.

• 1 page points its canonical at the homepage

  /home-collection declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  Elements (1)

• 2 linked pages hidden from search

  /health-packages and /lab-test are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  Elements (2)

• 2 pages share a title

  / and /home-collection all use the title “Best Pathology Lab & Diagnostic Centre | Dr. B. Lal Lab”. Search engines can't tell which page to show for a search, so each competes with the others.

  Elements (2)

• 3 pages without an H1

  /find-nearest-lab, /health-packages and /lab-test have no <h1> headline, so visitors and search engines get no clear main topic.

• 3 pages with very little text

  /find-nearest-lab, /milestones and /healthbulletin 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.

• 14 internal pages checked

  We fetched 14 pages linked from your homepage and read each the way a search engine does.

• 1 JavaScript error while loading

  1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.

• No HSTS header

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

• No Content-Security-Policy

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

• HTTP/1.1 only

  The server only offers HTTP/1.1, so browsers open several connections and load files more slowly. Most hosts and CDNs turn on HTTP/2 with a setting.

• No clickjacking protection

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

• No X-Content-Type-Options

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

• No Referrer-Policy

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

• No Permissions-Policy

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

• No security.txt

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

• No CAA record

  blallab.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

• DNSSEC is off

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

• Local business without LocalBusiness data

  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.

  View source

• No map or directions link

  There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

• No risk reducer

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

• About 885 words of copy

  The homepage carries about 885 words of visible text.

• Email authentication score: 90/100

  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.

• 5 trackers load before any consent

  5

  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.

• 5 cookies set on arrival

  5

  Opening the homepage sets 5 cookies (measured from a US location before any click).

• No consent tool detected

  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.

• 21 other companies contacted

  Loading the homepage contacts 21 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.