Website review, no card needed

apcerls.com logo

apcerls.com website review

Visit site (opens in a new tab)Reviewed 19 November 202646 issues · 90 checks

This review found 46 issues worth fixing on apcerls.com, 19 of them high impact, across 90 checks. The most urgent: reduce unused JavaScript. 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
6.3 s2.5 sMay 30Nov 145.9 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.0 s
Jun 6, 20263.2 s
Jun 13, 20263.5 s
Jun 20, 20264.0 s
Jun 27, 20264.6 s
Jul 4, 20265.1 s
Jul 11, 20265.3 s
Jul 18, 20265.2 s
Jul 25, 20265.0 s
Aug 1, 20265.1 s
Aug 8, 20265.3 s
Aug 15, 20265.5 s
Aug 22, 20265.6 s
Aug 29, 20265.6 s
Sep 5, 20265.4 s
Sep 12, 20265.2 s
Sep 19, 20264.9 s
Sep 26, 20264.8 s
Oct 3, 20265.0 s
Oct 10, 20265.0 s
Oct 17, 20265.1 s
Oct 24, 20265.1 s
Oct 31, 20265.5 s
Nov 7, 20265.8 s
Nov 14, 20265.9 s
Real-visitor tap response (INP)75th percentile, phones
194 ms143 msMay 30Nov 14188 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026171 ms
Jun 6, 2026160 ms
Jun 13, 2026150 ms
Jun 20, 2026152 ms
Jun 27, 2026150 ms
Jul 4, 2026156 ms
Jul 11, 2026169 ms
Jul 18, 2026167 ms
Jul 25, 2026164 ms
Aug 1, 2026164 ms
Aug 8, 2026155 ms
Aug 15, 2026150 ms
Aug 22, 2026150 ms
Aug 29, 2026152 ms
Sep 5, 2026149 ms
Sep 12, 2026158 ms
Sep 19, 2026162 ms
Sep 26, 2026161 ms
Oct 3, 2026171 ms
Oct 10, 2026172 ms
Oct 17, 2026176 ms
Oct 24, 2026179 ms
Oct 31, 2026186 ms
Nov 7, 2026184 ms
Nov 14, 2026188 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 apcerls.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. apcerls.com at 1.1 s1.1 s
  2. apcerls.com at 2.1 s2.1 s
  3. apcerls.com at 3.2 s3.2 s
  4. apcerls.com at 4.2 s4.2 s
  5. apcerls.com at 5.3 s5.3 s
  6. apcerls.com at 6.3 s6.3 s
  7. apcerls.com at 7.4 s7.4 s
  8. apcerls.com at 8.4 s8.4 s

Speed

10 to fix35
  • Reduce unused JavaScript

    7.0 s · 1.2 MB

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

  • Render-blocking requests

    2.6 s

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

  • Use efficient cache lifetimes

    1.8 s · 623 KiB

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

  • Reduce unused CSS

    1.1 s · 144 KiB

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

  • Mobile performance score: 35

    35/100

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

  • Main-thread work: 4.6 s

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

  • 8 third-party services on the page

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

  • Google CDN adds 960 ms

    960 ms

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

  • Google Tag Manager adds 420 ms

    420 ms

    Google Tag Manager costs a phone 420 ms of main-thread work and 517 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,863 HTML elements

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

  • 20 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Improve image delivery

    32 KiB

    1 image could be 32 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Legacy JavaScript

    6 KiB

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

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

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 8 ms

    8 ms

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

Core Web Vitals

12 to fix67
  • 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: 5.6 s

    5.6 s

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

  • Real-user FCP: 4.4 s

    4.4 s

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

  • Real-user TTFB: 2.6 s

    2.6 s

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

  • Largest Contentful Paint: 19.8 s

    19.8 s

    Your largest element takes 19.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to provide a seamless experience to the visi…”.

  • Time to Interactive: 25.4 s

    25.4 s

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

  • Speed Index: 14.9 s

    14.9 s

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

  • Total Blocking Time: 839 ms

    839 ms

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

  • First Contentful Paint: 3.4 s

    3.4 s

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

  • Largest content (LCP) got 88% slower for real visitors

    +88%

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

  • Cumulative Layout Shift: 0.125

    0.125

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

  • 3 images without width and height

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

  • Tap response (INP) got 12% slower for real visitors

    +12%

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

2 checks passed
  • Real-user INP: 137 ms

    137 ms

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

  • Real-user CLS: 0.04

    0.04

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

Images and page weight

3 to fix50
  • Page weight: 5.0 MB in 175 requests

    5.0 MB

    Your homepage downloads 5.0 MB in 175 requests on a phone: scripts 2.7 MB (57), images 769 KiB (36) and other files 737 KiB (38). Under 2 MB keeps phones on slow connections fast.

  • 8 images in older formats

    8 images (554 KiB) 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.

  • 1 image far larger than shown

    1 KiB

    1 image is downloaded at several times the size a phone draws it, for example disk-image-1.png at 578 px wide, shown at 192 px. Resized copies would save about 1 KiB.

  • 3 images below the first screen load straight away

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

  • About 1.4 g of CO₂ per visit

    1.43 g

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

Accessibility

7 to fix77
  • [role]s are not contained by their required parent element

    [role]s are not contained by their required parent element (5 elements).

  • Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

    Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (1 element).

  • 10 tap targets too small

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

  • Orphan list items

    Some list items are not inside a list.

  • 3 text elements with low contrast

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

  • 3 form fields without a label

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

  • Hidden but focusable

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

  • No main landmark

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

  • Headings skip levels

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

1 checks passed
  • Every image has alt text

    All 30 images in the HTML carry an alt attribute.

SEO

7 to fixGoogle 8569
  • No H1 headline

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

  • Title is long (90 characters)

    Your title is 90 characters, so Google will cut it off around 60: “Top Pharmacovigilance CRO Backed by Advanced PV Technology Solutions - APCER LIFE SCIENCES”.

  • 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 long (240 characters)

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

  • No social preview image

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

  • 10 links with vague text

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

  • 5 links crawlers can't follow

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

  • 78 internal links, 4 external

    The homepage links to 78 pages on apcerls.com and 4 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://www.apcerls.com/.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.apcerls.com/sitemap.xml.

AI search readiness

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

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

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,145 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

1 to fix95
  • 1 page without a meta description

    https://www.apcerls.com/rems has no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages slow to respond

    https://www.apcerls.com/psmf, https://www.apcerls.com/integrated-pv-mi, https://www.apcerls.com/medical-information, https://www.apcerls.com/integrated-response-center, https://www.apcerls.com/specialized-rems-contact-center and https://www.apcerls.com/medical-writing took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 30 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.

  • Titles are unique

    Every page we checked has its own title.

  • 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

2 to fixGoogle 9291
  • 1 JavaScript error while loading

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

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix79
  • Thin social proof

    Social proof on the homepage: 11 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • Only about 212 words

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

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

4 checks passed
  • Clear next step on the first screen

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

  • 12 calls to action

    The homepage has 12 calls to action, for example “Specialized REMS Contact Center”, “Contact” and “REGISTER NOW”.

  • 4 short forms

    4 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and LinkedIn Insight.

Privacy and tracking

  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and LinkedIn Insight (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

  • 9 cookies set on arrival

    9

    Opening the homepage sets 9 cookies, 2 of them by other companies (measured from a US location before any click).

  • 18 other companies contacted

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

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

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 apcerls.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
Joomla
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
AWS

Company

Headquarters
London

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 46 issues on apcerls.com, including 22 speed issues, 7 SEO issues and 3 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