Website review, no card needed
archpharmalabs.com website review
Visit site (opens in a new tab)Reviewed 27 October 202641 issues · 84 checks
This review found 41 issues worth fixing on archpharmalabs.com, 17 of them high impact, across 84 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
61DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.1 s |
| May 16, 2026 | 2.3 s |
| May 23, 2026 | 2.5 s |
| May 30, 2026 | 2.5 s |
| Jun 6, 2026 | 2.4 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.4 s |
| Oct 3, 2026 | 2.5 s |
| Oct 10, 2026 | 2.7 s |
| Oct 17, 2026 | 2.6 s |
| Oct 24, 2026 | 2.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 91 ms |
| May 16, 2026 | 91 ms |
| Jun 13, 2026 | 86 ms |
| Jun 20, 2026 | 94 ms |
| Jun 27, 2026 | 94 ms |
| Jul 4, 2026 | 86 ms |
| Jul 11, 2026 | 86 ms |
| Jul 18, 2026 | 84 ms |
| Jul 25, 2026 | 83 ms |
| Aug 1, 2026 | 83 ms |
| Aug 8, 2026 | 80 ms |
| Aug 15, 2026 | 82 ms |
| Aug 22, 2026 | 83 ms |
| Aug 29, 2026 | 83 ms |
| Sep 5, 2026 | 90 ms |
| Sep 12, 2026 | 81 ms |
| Sep 26, 2026 | 84 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
How it loaded on a phone
1.7 s
3.4 s
5.1 s
6.8 s
8.5 s
10.2 s
11.9 s
13.6 s
Speed
Use efficient cache lifetimes
2.0 s · 5.0 MB45 files are served with short cache lifetimes, so returning visitors download them again (5.0 MB).
Render-blocking requests
4.0 s13 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.0 s.
Font display
3.0 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 3.0 s).
Reduce unused CSS
1.3 s · 272 KiBAbout 272 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.3 s faster on a phone.
Mobile performance score: 39
39/100Your mobile performance score is 39 (desktop: 56). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Improve image delivery
3.2 MB13 images could be 3.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
5 third-party services on the page
5 third-party services load with your homepage (Google Tag Manager, Google Analytics and lfeeder.com and others), adding 254 KiB and 139 ms of main-thread time.
Reduce unused JavaScript
135 KiBAbout 135 KiB of JavaScript is downloaded but never used on this page.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 92 ms. During a long task the page ignores taps.
Minify CSS
28 KiB28 KiB could be saved by minifying CSS.
Minify JavaScript
25 KiB25 KiB could be saved by minifying JavaScript.
Document request latency
20 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
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.
2 checks passed
Main-thread work: 0.6 s
A phone's processor spends 0.6 s on main-thread work while loading, 251 ms of it running JavaScript. That is comfortably low.
Server response: 15 ms
15 msYour server sent the HTML in 15 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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 CLS: 1.00
1.00For real visitors the layout shifts by 1.00 (75th percentile). Good is under 0.1.
Speed Index: 19.5 s
19.5 sVisually, the page fills in at 19.5 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 1.007
1.007The layout shifts by 1.007 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 4.4 s
4.4 sThe first text or image appears after 4.4 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 5.0 s
5.0 sYour largest element takes 5.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We are a Pharmaceutical Company aligned across two business…”. Most of its time is element render delay (5.5 s).
Time to Interactive: 9.3 s
9.3 sThe page becomes fully interactive after 9.3 s. Good is under 3.8 s.
Real-user LCP: 3.0 s
3.0 sReal visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.2 s
2.2 sReal visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.
11 images without width and height
11 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 91 ms to 84 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Total Blocking Time: 21 ms
21 msScripts block the page for only 21 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 5.3 MB in 54 requests
5.3 MBYour homepage downloads 5.3 MB in 54 requests on a phone: images 4.3 MB (20), scripts 477 KiB (17) and stylesheets 323 KiB (11). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
merven2.jpg weighs 552 KiB. On a phone connection a single image that size takes seconds.
9 images in older formats
9 images (2.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.
7 images below the first screen load straight away
7 images further down the page (2.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.5 g of CO₂ per visit
1.49 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.49 g of CO₂e: 179.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
10 text elements with low contrast
10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h4, h1 → h4 and h1 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
35 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 35 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (15 characters)
Your title is only 15 characters: “Arch-Pharmalabs”. 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.
Meta description is short (48 characters)
Your meta description is only 48 characters: “Responsive Bootstrap Personal Portfolio Template”. 70 to 160 characters is enough to sell the click.
7 H1 headlines
There are 7 <h1> headlines (“RESILIENCE”, “CHALLENGE” and “Never Say Die Attitude”). One clear main headline is easier for people and search engines.
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://archpharmalabs.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at archpharmalabs.com/robots.txt, the first file search crawlers ask for.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
37 internal links, 1 external
The homepage links to 37 pages on archpharmalabs.com and 1 external page.
AI search readiness
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.
No llms.txt
There is no https://archpharmalabs.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.
2 checks passed
AI answer engines may read the site
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (330 words), so crawlers that don't run JavaScript still read it.
Other pages
16 pages share a title
/, https://archpharmalabs.com/careers.php, https://archpharmalabs.com/contact-us.php, https://archpharmalabs.com/vitalife-site-gurgaon.php, https://archpharmalabs.com/oncology-site-tarapur.php and https://archpharmalabs.com/dombivli-site-mumbai.php and 10 others all use the title “Arch-Pharmalabs”. Search engines can't tell which page to show for a search, so each competes with the others.
15 pages share a meta description
https://archpharmalabs.com/careers.php, https://archpharmalabs.com/contact-us.php, https://archpharmalabs.com/vitalife-site-gurgaon.php, https://archpharmalabs.com/oncology-site-tarapur.php, https://archpharmalabs.com/dombivli-site-mumbai.php and https://archpharmalabs.com/api-quality-regulations.php and 9 others use the same meta description. A description written for each page earns more clicks.
5 pages with very little text
https://archpharmalabs.com/careers.php, https://archpharmalabs.com/contact-us.php, https://archpharmalabs.com/api-accrediations.php, https://archpharmalabs.com/api-gallery.php and https://archpharmalabs.com/intermediate-accrediations.php 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 24 found) and read each the way a search engine does.
6 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
Every page has an H1
Each page we checked has a main headline.
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
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_BLOCKED_BY_RESPONSE.NotSameOrigin”.
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 (“Mixed content”).
2 checks passed
Tap targets are thumb-sized
5 of 5 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 330 words of copy
The homepage carries about 330 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact Us”.
1 call to action
The homepage has 1 call to action, for example “Contact Us”.
1 short form
A short form (4 fields at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads 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.
5 cookies set on arrival
5Opening 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.
7 other companies contacted
Loading the homepage contacts 7 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 archpharmalabs.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Analytics
- Hosting
- TATA Communications formerly VSNL is Leading ISP
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on archpharmalabs.com, including 16 speed issues, 8 SEO issues and 1 conversion gap. 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.