Website review, no card needed

emeraldclinical.com logo

emeraldclinical.com website review

Visit site (opens in a new tab)Reviewed 29 October 202632 issues · 79 checks

This review found 32 issues worth fixing on emeraldclinical.com, 11 of them high impact, across 79 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
4.5 s2.0 sMay 9Oct 243.5 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.1 s
May 16, 20262.8 s
May 23, 20262.6 s
May 30, 20262.5 s
Jun 6, 20262.4 s
Jun 13, 20262.4 s
Jun 20, 20262.6 s
Jun 27, 20262.7 s
Jul 4, 20262.8 s
Jul 11, 20262.8 s
Jul 18, 20262.8 s
Jul 25, 20262.9 s
Aug 1, 20262.8 s
Aug 8, 20262.8 s
Aug 15, 20262.6 s
Aug 22, 20262.4 s
Aug 29, 20262.3 s
Sep 5, 20262.5 s
Sep 12, 20262.8 s
Sep 19, 20263.5 s
Sep 26, 20263.9 s
Oct 3, 20264.2 s
Oct 10, 20264.2 s
Oct 17, 20263.9 s
Oct 24, 20263.5 s
Real-visitor tap response (INP)75th percentile, phones
161 ms126 msMay 9Oct 24136 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026157 ms
May 16, 2026150 ms
May 23, 2026145 ms
May 30, 2026137 ms
Jun 6, 2026139 ms
Jun 13, 2026140 ms
Jun 20, 2026148 ms
Jun 27, 2026151 ms
Jul 4, 2026153 ms
Jul 11, 2026151 ms
Jul 18, 2026146 ms
Jul 25, 2026146 ms
Aug 1, 2026139 ms
Aug 8, 2026134 ms
Aug 15, 2026130 ms
Aug 22, 2026130 ms
Aug 29, 2026132 ms
Sep 5, 2026141 ms
Sep 12, 2026146 ms
Sep 19, 2026144 ms
Sep 26, 2026148 ms
Oct 3, 2026137 ms
Oct 10, 2026137 ms
Oct 17, 2026138 ms
Oct 24, 2026136 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 emeraldclinical.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. emeraldclinical.com at 0.4 s0.4 s
  2. emeraldclinical.com at 0.8 s0.8 s
  3. emeraldclinical.com at 1.1 s1.1 s
  4. emeraldclinical.com at 1.5 s1.5 s
  5. emeraldclinical.com at 1.9 s1.9 s
  6. emeraldclinical.com at 2.3 s2.3 s
  7. emeraldclinical.com at 2.6 s2.6 s
  8. emeraldclinical.com at 3.0 s3.0 s

Speed

10 to fix51
  • Reduce unused JavaScript

    1.5 s · 230 KiB

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

  • Render-blocking requests

    1.4 s

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

  • Mobile performance score: 51

    51/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, cloudfront.net and Clarity and others), adding 734 KiB and 823 ms of main-thread time.

  • Google Tag Manager adds 582 ms

    582 ms

    Google Tag Manager costs a phone 582 ms of main-thread work and 530 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.

  • Use efficient cache lifetimes

    450 ms · 69 KiB

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

  • Reduce unused CSS

    450 ms · 41 KiB

    About 41 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Improve image delivery

    300 ms · 80 KiB

    1 image could be 80 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

  • Minify JavaScript

    300 ms · 26 KiB

    26 KiB could be saved by minifying JavaScript.

  • Main-thread work: 2.4 s

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

  • 7 long tasks on the main thread

    7 long tasks block the main thread while loading, the longest for 238 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).

  • Legacy JavaScript

    8 KiB

    Polyfills for old browsers add 8 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

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 5 ms

    5 ms

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

Core Web Vitals

12 to fix33
  • 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.5 s

    5.5 s

    Real visitors wait 5.5 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.4 s

    2.4 s

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

  • Largest Contentful Paint: 15.5 s

    15.5 s

    Your largest element takes 15.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Emerald Clinical Trials is a global leader in clinical rese…”.

  • Time to Interactive: 15.9 s

    15.9 s

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

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • Speed Index: 5.8 s

    5.8 s

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

  • Real-user CLS: 0.13

    0.13

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

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

    +26%

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

  • Total Blocking Time: 492 ms

    492 ms

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

  • 10 images without width and height

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

3 checks passed
  • Real-user INP: 173 ms

    173 ms

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

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

    -11%

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

  • Cumulative Layout Shift: 0.071

    0.071

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

Images and page weight

3 to fix68
  • Page weight: 2.5 MB in 98 requests

    2.5 MB

    Your homepage downloads 2.5 MB in 98 requests on a phone: images 1.6 MB (31), scripts 784 KiB (23) and stylesheets 84 KiB (23). Under 2 MB keeps phones on slow connections fast.

  • 8 images below the first screen load straight away

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

  • 1 image far larger than shown

    24 KiB

    1 image is downloaded at several times the size a phone draws it, for example vid-screenshot-hoempage-update-2026-03-29.jpg at 1,202 px wide, shown at 342 px. Resized copies would save about 24 KiB.

  • 4 images in older formats

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

  • About 0.7 g of CO₂ per visit

    0.71 g

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

Accessibility

2 to fixGoogle 9898
  • ARIA role should be appropriate for the element (4 elements)

    ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.

  • Elements marked as presentational should be consistently ignored (4 elements)

    Elements marked as presentational should be consistently ignored: 4 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 22 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

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

SEO

1 to fixGoogle 9298
  • 4 links with vague text

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

  • 150 internal links, 10 external

    The homepage links to 150 pages on emeraldclinical.com and 10 external pages.

8 checks passed
  • Meta description: 155 characters

    Your meta description is 155 characters: “We are a global clinical research organization with fresh perspectives to solving challenges. Discover unparalleled qua…”.

  • One H1 headline

    Your main headline reads: “APAC Based Global CRODriven by Science, Defined by Excellence”.

  • Title: 64 characters

    Your title is a healthy 64 characters: “Leading Global Clinical Research Organization | Emerald Clinical”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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://emeraldclinical.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

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

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.

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

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

Other pages

2 to fix88
  • 1 linked page hidden from search

    https://emeraldclinical.com/register-as-a-research-professional is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 9 pages without a meta description

    https://emeraldclinical.com/staff-member/spotlight/ari-vanderwalde, https://emeraldclinical.com/staff-member/spotlight/jonathan-barratt, https://emeraldclinical.com/staff-member/spotlight/herbert-h-loong, https://emeraldclinical.com/staff-member/spotlight/david-thomas, https://emeraldclinical.com/staff-member/spotlight/chee-kay-cheung and https://emeraldclinical.com/staff-member/spotlight/hernan-trimarchi and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

Google 100100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • 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 direct contact details

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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 1,216 words of copy

    The homepage carries about 1,216 words of visible text.

3 checks passed
  • 11 calls to action

    The homepage has 11 calls to action, for example “Register as a Research Expert”, “Contact us” and “Request a proposal”.

  • Social proof on the page

    Social proof on the homepage: 4 testimonial or review blocks, 1 customer or partner logo and “served 700k+ patients”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Microsoft Clarity (measured from a US location before any click). A consent tool (CookieYes) 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 (measured from a US location before any click).

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

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) 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 emeraldclinical.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
Analytics
Google Tag Manager
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on emeraldclinical.com, including 22 speed issues, 1 SEO issue 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