Website review, no card needed

apexpharmaeg.com logo

apexpharmaeg.com website review

Visit site (opens in a new tab)Reviewed 4 November 202635 issues · 79 checks

This review found 35 issues worth fixing on apexpharmaeg.com, 19 of them high impact, across 79 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
9.3 s6.3 sMay 16Oct 316.6 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20267.8 s
May 23, 20267.4 s
May 30, 20267.4 s
Jun 6, 20267.4 s
Jun 13, 20267.5 s
Jun 20, 20268.2 s
Jun 27, 20268.4 s
Jul 4, 20267.8 s
Jul 11, 20267.8 s
Jul 18, 20267.7 s
Jul 25, 20267.5 s
Aug 1, 20267.9 s
Aug 8, 20268.2 s
Aug 15, 20268.5 s
Aug 22, 20268.4 s
Aug 29, 20268.1 s
Sep 5, 20268.2 s
Sep 12, 20268.1 s
Sep 19, 20268.4 s
Sep 26, 20268.9 s
Oct 3, 20268.9 s
Oct 10, 20268.9 s
Oct 17, 20268.8 s
Oct 24, 20267.8 s
Oct 31, 20266.6 s
Real-visitor tap response (INP)75th percentile, phones
314 ms104 msMay 16Oct 31128 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026276 ms
May 23, 2026282 ms
May 30, 2026290 ms
Jun 6, 2026290 ms
Jun 13, 2026272 ms
Jun 20, 2026266 ms
Jun 27, 2026225 ms
Jul 4, 2026216 ms
Jul 11, 2026203 ms
Jul 18, 2026186 ms
Jul 25, 2026181 ms
Aug 1, 2026170 ms
Aug 8, 2026161 ms
Aug 15, 2026161 ms
Aug 22, 2026163 ms
Aug 29, 2026146 ms
Sep 5, 2026157 ms
Sep 12, 2026166 ms
Sep 19, 2026158 ms
Sep 26, 2026170 ms
Oct 3, 2026171 ms
Oct 10, 2026148 ms
Oct 17, 2026149 ms
Oct 24, 2026136 ms
Oct 31, 2026128 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 apexpharmaeg.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. apexpharmaeg.com at 0.5 s0.5 s
  2. apexpharmaeg.com at 1.1 s1.1 s
  3. apexpharmaeg.com at 1.6 s1.6 s
  4. apexpharmaeg.com at 2.1 s2.1 s
  5. apexpharmaeg.com at 2.6 s2.6 s
  6. apexpharmaeg.com at 3.1 s3.1 s
  7. apexpharmaeg.com at 3.7 s3.7 s
  8. apexpharmaeg.com at 4.2 s4.2 s

Speed

7 to fix57
  • Use efficient cache lifetimes

    5.2 s · 8.2 MB

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

  • Render-blocking requests

    5.8 s

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

  • Reduce unused JavaScript

    1.1 s · 290 KiB

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

  • Reduce unused CSS

    1.1 s · 234 KiB

    About 234 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.

  • Improve image delivery

    4.2 MB

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

  • Mobile performance score: 57

    57/100

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

  • Main-thread work: 2.8 s

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

  • Minify JavaScript

    150 ms · 28 KiB

    28 KiB could be saved by minifying JavaScript.

  • 6 long tasks on the main thread

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (Google Maps and Google Fonts), adding 236 KiB and 61 ms of main-thread time.

  • Legacy JavaScript

    26 KiB

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

  • Minify CSS

    8 KiB

    8 KiB could be saved by minifying CSS.

  • 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: 63 ms

    63 ms

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

Core Web Vitals

8 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: 7.4 s

    7.4 s

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

  • Real-user FCP: 5.3 s

    5.3 s

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

  • Real-user TTFB: 2.3 s

    2.3 s

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

  • Largest Contentful Paint: 14.7 s

    14.7 s

    Your largest element takes 14.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Apex Pharma renews EDA accreditation in accordance with Lev…”.

  • Time to Interactive: 15.5 s

    15.5 s

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

  • First Contentful Paint: 5.0 s

    5.0 s

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

  • Speed Index: 9.9 s

    9.9 s

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

  • Largest content (LCP) held steady for real visitors

    -5%

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

5 checks passed
  • Real-user INP: 128 ms

    128 ms

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

  • Real-user CLS: 0.02

    0.02

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

  • Tap response (INP) got 53% faster for real visitors

    -53%

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

  • Total Blocking Time: 72 ms

    72 ms

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

  • Cumulative Layout Shift: 0.033

    0.033

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

Images and page weight

5 to fix18
  • Page weight: 8.4 MB in 152 requests

    8.4 MB

    Your homepage downloads 8.4 MB in 152 requests on a phone: images 7.1 MB (19), scripts 731 KiB (66) and stylesheets 365 KiB (59). Under 2 MB keeps phones on slow connections fast.

  • 4 images over 500 KB

    4 images weigh 5.1 MB together. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    1.7 MB

    1 image is downloaded at several times the size a phone draws it, for example 18-11-2025.png at 1,326 px wide, shown at 173 px. Resized copies would save about 1.7 MB.

  • 12 images in older formats

    12 images (6.9 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.

  • 8 images below the first screen load straight away

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

  • About 2.4 g of CO₂ per visit

    2.37 g

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

Accessibility

4 to fixGoogle 8893
  • 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.

  • 8 tap targets too small

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

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

  • 8 links without text

    8 visible links have no text or label, so screen readers cannot say where they go.

2 checks passed
  • Every image has alt text

    All 49 images in the HTML carry an alt attribute.

  • 39 automated accessibility rules passed

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

SEO

6 to fixGoogle 9270
  • No H1 headline

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

  • Title is short (11 characters)

    Your title is only 11 characters: “APEX Pharma”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 29 links with vague text

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

  • Meta description is long (242 characters)

    Your meta description is 242 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:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

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

  • No X (Twitter) card tag

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

  • 90 internal links, 0 external

    The homepage links to 90 pages on apexpharmaeg.com and 0 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://apexpharmaeg.com/.

  • Structured data in place

    Structured data found: Organization, Person and WebSite.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles) and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://apexpharmaeg.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

    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,106 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 1 page without a meta description

    https://apexpharmaeg.com/category/newsletter has no meta description, so Google writes the search snippet from whatever text it finds.

  • 13 pages without an H1

    https://apexpharmaeg.com/corporate-identity, https://apexpharmaeg.com/chairman-message, https://apexpharmaeg.com/plant-facility, https://apexpharmaeg.com/quality-management-system, https://apexpharmaeg.com/what-is-pharmacovigilance-pv and https://apexpharmaeg.com/quality and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages slow to respond

    https://apexpharmaeg.com/training-development-culture and https://apexpharmaeg.com/contact-us took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • 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

Google 100100
2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix70
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 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 794 words of copy

    The homepage carries about 794 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

3 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact us”, “Get In Touch” and “Contact Us”.

  • 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: 2 testimonial or review blocks and “More Than 1200 Companies”.

Privacy and tracking

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

  • 3 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 apexpharmaeg.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
WordPress
Framework
jQuery
Hosting
Newfold Digital

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on apexpharmaeg.com, including 15 speed issues, 6 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