Website review, no card needed

hplbd.com logo

hplbd.com website review

Visit site (opens in a new tab)Reviewed 31 October 202654 issues · 95 checks

This review found 54 issues worth fixing on hplbd.com, 18 of them high impact, across 95 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
7.1 s6.3 sMay 9Oct 246.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20266.4 s
May 16, 20266.5 s
May 23, 20266.6 s
May 30, 20266.8 s
Jun 6, 20266.9 s
Jun 13, 20267.0 s
Jun 20, 20266.9 s
Jun 27, 20266.6 s
Jul 4, 20266.5 s
Jul 11, 20266.4 s
Jul 18, 20266.4 s
Jul 25, 20266.6 s
Aug 1, 20266.7 s
Aug 8, 20266.7 s
Aug 15, 20266.7 s
Aug 22, 20266.7 s
Aug 29, 20266.6 s
Sep 5, 20266.5 s
Sep 12, 20266.6 s
Sep 19, 20266.6 s
Sep 26, 20266.7 s
Oct 3, 20266.8 s
Oct 10, 20266.7 s
Oct 17, 20266.7 s
Oct 24, 20266.8 s
Real-visitor tap response (INP)75th percentile, phones
193 ms161 msMay 9Oct 24179 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026165 ms
May 16, 2026165 ms
May 23, 2026166 ms
May 30, 2026169 ms
Jun 6, 2026177 ms
Jun 13, 2026182 ms
Jun 20, 2026180 ms
Jun 27, 2026178 ms
Jul 4, 2026176 ms
Jul 11, 2026174 ms
Jul 18, 2026174 ms
Jul 25, 2026174 ms
Aug 1, 2026173 ms
Aug 8, 2026173 ms
Aug 15, 2026172 ms
Aug 22, 2026177 ms
Aug 29, 2026177 ms
Sep 5, 2026176 ms
Sep 12, 2026179 ms
Sep 19, 2026178 ms
Sep 26, 2026182 ms
Oct 3, 2026189 ms
Oct 10, 2026181 ms
Oct 17, 2026180 ms
Oct 24, 2026179 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of hplbd.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. hplbd.com at 1.2 s1.2 s
  2. hplbd.com at 2.5 s2.5 s
  3. hplbd.com at 3.7 s3.7 s
  4. hplbd.com at 4.9 s4.9 s
  5. hplbd.com at 6.2 s6.2 s
  6. hplbd.com at 7.4 s7.4 s
  7. hplbd.com at 8.6 s8.6 s
  8. hplbd.com at 9.9 s9.9 s

Speed

13 to fix53
  • Use efficient cache lifetimes

    9.6 s · 13.2 MB

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

  • Render-blocking requests

    8.0 s

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

  • Reduce unused JavaScript

    6.2 s · 1.1 MB

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

  • Reduce unused CSS

    6.0 s · 1.2 MB

    About 1.2 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 6.0 s faster on a phone.

  • Main-thread work: 7.6 s

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

  • Improve image delivery

    150 ms · 7.2 MB

    17 images could be 7.2 MB 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Vimeo and Other Google APIs/SDKs and others), adding 5.5 MB and 898 ms of main-thread time.

  • Minify CSS

    900 ms · 180 KiB

    180 KiB could be saved by minifying CSS.

  • Mobile performance score: 53

    53/100

    Your mobile performance score is 53. Pages that score under 90 lose visitors before the first paint.

  • Vimeo adds 246 ms

    246 ms

    Vimeo costs a phone 246 ms of main-thread work and 4.2 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.

  • Minify JavaScript

    450 ms · 77 KiB

    77 KiB could be saved by minifying JavaScript.

  • YouTube adds 353 ms

    353 ms

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

  • 1,619 HTML elements

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

  • Legacy JavaScript

    150 ms · 26 KiB

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

  • 11 long tasks on the main thread

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

  • Document request latency

    122 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Font display

    100 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 73 ms

    73 ms

    Your server sent the HTML in 73 ms, well inside Google's 600 ms guideline.

Core Web Vitals

11 to fix0
  • Fails Core Web Vitals for real visitors

    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-user LCP: 8.8 s

    8.8 s

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

  • Real-user FCP: 5.9 s

    5.9 s

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

  • First Contentful Paint: 16.8 s

    16.8 s

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

  • Largest Contentful Paint: 36.5 s

    36.5 s

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

  • Speed Index: 17.9 s

    17.9 s

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

  • Time to Interactive: 37.8 s

    37.8 s

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

  • Real-user INP: 246 ms

    246 ms

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

  • Real-user CLS: 0.25

    0.25

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

  • Real-user TTFB: 1.4 s

    1.4 s

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

  • 23 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +9%

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

  • Largest content (LCP) held steady for real visitors

    +5%

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

2 checks passed
  • Total Blocking Time: 155 ms

    155 ms

    Scripts block the page for only 155 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

5 to fix18
  • Page weight: 18.9 MB in 159 requests

    18.9 MB

    Your homepage downloads 18.9 MB in 159 requests on a phone: images 11.5 MB (63), other files 3.7 MB (35) and scripts 2.0 MB (31). Under 2 MB keeps phones on slow connections fast.

  • 7 images over 500 KB

    7 images weigh 7.6 MB together. On a phone connection a single image that size takes seconds.

  • 13 images far larger than shown

    5.5 MB

    13 images are downloaded at several times the size a phone draws them, for example achieves-prestigious-kano-bstqm-quality-award-kbqa-a-first-f at 1,400 px wide, shown at 186 px. Resized copies would save about 5.5 MB.

  • 39 images in older formats

    39 images (11.3 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.

  • 11 images below the first screen load straight away

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

  • About 5.4 g of CO₂ per visit

    5.36 g

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

Accessibility

6 to fixGoogle 9891
  • 12 images without alt text

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

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 11 form fields without a label

    11 form fields have no label, so screen readers announce an empty box and autofill guesses.

1 checks passed
  • 35 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 39 WCAG 2.2 A/AA and best-practice rules on the phone render: 35 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

9 to fixGoogle 7557
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

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

  • Title is short (26 characters)

    Your title is only 26 characters: “Healthcare Pharmaceuticals”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • No canonical URL

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

  • No social preview image

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

  • No XML sitemap

    No XML sitemap at https://www.hplbd.com/sitemap.xml, so Google discovers your pages only by following links.

  • 8 links with vague text

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

  • 2 links crawlers can't follow

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

  • No X (Twitter) card tag

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

  • 216 internal links, 15 external

    The homepage links to 216 pages on hplbd.com and 15 external pages.

1 checks passed
  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix83
  • No Organization structured data

    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.

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • llms.txt published

    The site publishes https://www.hplbd.com/llms.txt (1 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix83
  • 6 pages share 2 titles

    https://www.hplbd.com/Products, https://www.hplbd.com/Category/30, https://www.hplbd.com/Category/61 and https://www.hplbd.com/Category/73 all use the title “Products | Healthcare Pharmaceuticals”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages without a meta description

    https://www.hplbd.com/About, https://www.hplbd.com/Products, https://www.hplbd.com/Facilities, https://www.hplbd.com/Research-Development, https://www.hplbd.com/Pipeline and https://www.hplbd.com/Quality-Management-System and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 12 pages without an H1

    https://www.hplbd.com/About, https://www.hplbd.com/Products, https://www.hplbd.com/Facilities, https://www.hplbd.com/Pipeline, https://www.hplbd.com/Global-Operation and https://www.hplbd.com/Newsroom and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.hplbd.com/Gallery and https://www.hplbd.com/Career 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.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 5088
  • 8 third-party cookies

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “$ is not defined”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    33 of 33 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix88
  • 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.

  • Only about 119 words

    The homepage has only about 119 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact” and “| Contact”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.

  • 7 cookies set on arrival

    7

    Opening the homepage sets 7 cookies, 3 of them by other companies (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.

  • 24 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at hplbd.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2024.

Stack

Framework
jQuery
Analytics
Google Analytics
Hosting
Network Solutions Hosting

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 54 issues on hplbd.com, including 24 speed issues, 9 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25