Website review, no card needed

allucent.com logo

allucent.com website review

Visit site (opens in a new tab)Reviewed 20 October 202642 issues · 91 checks

This review found 42 issues worth fixing on allucent.com, 20 of them high impact, across 91 checks. The most urgent: improve image delivery. 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
3.1 s2.3 sMay 2Oct 172.6 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.0 s
May 9, 20263.0 s
May 16, 20263.0 s
May 23, 20263.0 s
May 30, 20263.0 s
Jun 6, 20262.8 s
Jun 13, 20262.6 s
Jun 20, 20262.6 s
Jun 27, 20262.4 s
Jul 4, 20262.5 s
Jul 11, 20262.5 s
Jul 18, 20262.5 s
Jul 25, 20262.6 s
Aug 1, 20262.6 s
Aug 8, 20262.6 s
Aug 15, 20262.6 s
Aug 22, 20262.7 s
Aug 29, 20262.6 s
Sep 5, 20262.6 s
Sep 12, 20262.5 s
Sep 19, 20262.4 s
Sep 26, 20262.4 s
Oct 3, 20262.4 s
Oct 10, 20262.6 s
Oct 17, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
149 ms117 msMay 2Oct 17139 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026130 ms
May 9, 2026132 ms
May 16, 2026137 ms
May 23, 2026134 ms
May 30, 2026133 ms
Jun 6, 2026133 ms
Jun 13, 2026137 ms
Jun 20, 2026142 ms
Jun 27, 2026144 ms
Jul 4, 2026145 ms
Jul 11, 2026138 ms
Jul 18, 2026132 ms
Jul 25, 2026131 ms
Aug 1, 2026132 ms
Aug 8, 2026134 ms
Aug 15, 2026127 ms
Aug 22, 2026125 ms
Aug 29, 2026121 ms
Sep 5, 2026125 ms
Sep 12, 2026132 ms
Sep 19, 2026136 ms
Sep 26, 2026136 ms
Oct 3, 2026137 ms
Oct 10, 2026139 ms
Oct 17, 2026139 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 allucent.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

10 to fix33
  • Improve image delivery

    15.1 s · 2.6 MB

    5 images could be 2.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 15.1 s faster on a phone.

  • Reduce unused JavaScript

    5.5 s · 832 KiB

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

  • Render-blocking requests

    2.5 s

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

  • Mobile performance score: 33

    33/100

    Your mobile performance score is 33 (desktop: 49). 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.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google CDN, Accessibe Accessibility Overlay and Hubspot and others), adding 14.5 MB and 1.2 s of main-thread time.

  • Vimeo adds 0 ms

    0 ms

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

  • Use efficient cache lifetimes

    800 ms · 190 KiB

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

  • Google CDN adds 684 ms

    684 ms

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

  • 19 long tasks on the main thread

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

  • Reduce unused CSS

    10 KiB

    About 10 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    9 KiB

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

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 6 ms

    6 ms

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

Core Web Vitals

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

  • First Contentful Paint: 10.5 s

    10.5 s

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

  • Largest Contentful Paint: 26.1 s

    26.1 s

    Your largest element takes 26.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Our A-Team of former regulators, leading scientists, and se…”.

  • Time to Interactive: 27.4 s

    27.4 s

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

  • Speed Index: 10.5 s

    10.5 s

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

  • Total Blocking Time: 1.1 s

    1.1 s

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

  • Real-user LCP: 2.6 s

    2.6 s

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • 4 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +6%

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

4 checks passed
  • Real-user INP: 161 ms

    161 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Largest content (LCP) got 15% faster for real visitors

    -15%

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

  • 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: 24.6 MB in 49 requests

    24.6 MB

    Your homepage downloads 24.6 MB in 49 requests on a phone: media 19.5 MB (6), images 2.7 MB (13) and scripts 1.8 MB (14). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

    3 images weigh 2.6 MB together. On a phone connection a single image that size takes seconds.

  • 4 images far larger than shown

    2.2 MB

    4 images are downloaded at several times the size a phone draws them, for example Clinical-pharmacology-modeling-and-simulation.jpg at 2,121 px wide, shown at 303 px. Resized copies would save about 2.2 MB.

  • 3 images below the first screen load straight away

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

  • 1 image in older formats

    1 image (1.3 MB) is 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 7.0 g of CO₂ per visit

    6.98 g

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

Accessibility

9 to fixGoogle 8488
  • Required ARIA attributes must be provided (11 elements)

    Required ARIA attributes must be provided: 11 elements on the page fail this check, rated critical by axe-core.

  • Invalid ARIA attributes

    2 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • Interactive controls must not be nested (11 elements)

    Interactive controls must not be nested: 11 elements on the page fail this check, rated serious by axe-core.

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

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

    All page content should be contained by landmarks: 39 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.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • ARIA role should be appropriate for the element (9 elements)

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 50 automated accessibility rules passed

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

SEO

1 to fixGoogle 8598
  • 9 links with vague text

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

  • 172 internal links, 4 external

    The homepage links to 172 pages on allucent.com and 4 external pages.

8 checks passed
  • Meta description: 150 characters

    Your meta description is 150 characters: “Global contract research organization delivering CRO services, regulatory support, and clinical development solutions f…”.

  • One H1 headline

    Your main headline reads: “A Full-Service Global Specialty CRO Purpose Built for Small and Mid-Size Biopharma”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “Contract Research Organization for Biopharma & Biotech”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, 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://www.allucent.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.allucent.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 (2,140 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 1 page slow to respond

    https://www.allucent.com/solutions/clinical-pharmacology-services took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

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

  • 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

1 to fixGoogle 9293
  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Unrecognized Content-Security-Policy directive 'prefetch-src'.”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix63
  • 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.

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

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • A 20-field form

    Your longest form asks for 20 fields (9 required). Every extra field lowers completion.

  • 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 opening hours

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

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

  • About 1,495 words of copy

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

3 checks passed
  • 18 calls to action

    The homepage has 18 calls to action, for example “Schedule a Consultation”, “Study Start-Up & Site Feasibility” and “Contact Us”.

  • Social proof on the page

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

  • Analytics in place

    Analytics detected: Google Tag Manager and HubSpot.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads 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.

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 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.

  • 10 other companies contacted

    Loading the homepage contacts 10 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 allucent.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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on allucent.com, including 20 speed issues, 1 SEO issue and 5 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