Website review, no card needed

apellis.com logo

apellis.com website review

Visit site (opens in a new tab)Reviewed 29 October 202627 issues · 75 checks

This review found 27 issues worth fixing on apellis.com, 11 of them high impact, across 75 checks. The most urgent: render-blocking requests. 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
1.7 s871 msMay 9Oct 241.6 s
Show as table
DateReal-visitor load time (LCP)
May 9, 2026970 ms
May 16, 2026969 ms
May 23, 20261.0 s
May 30, 20261.1 s
Jun 6, 20261.2 s
Jun 13, 20261.4 s
Jun 20, 20261.5 s
Jun 27, 20261.5 s
Jul 4, 20261.5 s
Jul 11, 20261.5 s
Jul 18, 20261.4 s
Jul 25, 20261.4 s
Aug 1, 20261.4 s
Aug 8, 20261.4 s
Aug 15, 20261.3 s
Aug 22, 20261.3 s
Aug 29, 20261.2 s
Sep 5, 20261.2 s
Sep 12, 20261.3 s
Sep 19, 20261.4 s
Sep 26, 20261.5 s
Oct 3, 20261.6 s
Oct 10, 20261.6 s
Oct 17, 20261.6 s
Oct 24, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
96 ms71 msMay 9Oct 2487 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202682 ms
May 16, 202679 ms
May 23, 202681 ms
May 30, 202683 ms
Jun 6, 202684 ms
Jun 13, 202688 ms
Jun 20, 202686 ms
Jun 27, 202688 ms
Jul 4, 202689 ms
Jul 11, 202689 ms
Jul 18, 202693 ms
Jul 25, 202682 ms
Aug 1, 202682 ms
Aug 8, 202680 ms
Aug 15, 202678 ms
Aug 22, 202680 ms
Aug 29, 202674 ms
Sep 5, 202677 ms
Sep 12, 202684 ms
Sep 19, 202684 ms
Sep 26, 202686 ms
Oct 3, 202690 ms
Oct 10, 202687 ms
Oct 17, 202687 ms
Oct 24, 202687 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 apellis.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

4 to fix63
  • Render-blocking requests

    1.4 s

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

  • Reduce unused JavaScript

    1.0 s · 203 KiB

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

  • Mobile performance score: 63

    63/100

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

  • Improve image delivery

    450 ms · 119 KiB

    4 images could be 119 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, userway.org and cookiehub.eu and others), adding 561 KiB and 221 ms of main-thread time.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 85 ms. During a long task the page ignores taps.

  • Use efficient cache lifetimes

    28 KiB

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

  • Reduce unused CSS

    16 KiB

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

  • Legacy JavaScript

    11 KiB

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

2 checks passed
  • Main-thread work: 0.7 s

    A phone's processor spends 0.7 s on main-thread work while loading, 372 ms of it running JavaScript. That is comfortably low.

  • Server response: 21 ms

    21 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 7.6 s

    7.6 s

    Your largest element takes 7.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “glasses”.

  • First Contentful Paint: 3.8 s

    3.8 s

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

  • Time to Interactive: 7.6 s

    7.6 s

    The page becomes fully interactive after 7.6 s. Good is under 3.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.

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

    +65%

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    +8%

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

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.8 s

    1.8 s

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

  • Real-user INP: 84 ms

    84 ms

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

  • Real-user CLS: 0.08

    0.08

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

  • Real-user FCP: 1.8 s

    1.8 s

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

  • Real-user TTFB: 628 ms

    628 ms

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 35 ms

    35 ms

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

Images and page weight

1 to fix90
  • 1 image far larger than shown

    37 KiB

    1 image is downloaded at several times the size a phone draws it, for example homepage-cta-4.jpg at 2,160 px wide, shown at 390 px. Resized copies would save about 37 KiB.

  • 4 images in older formats

    4 images (187 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.2 g of CO₂ per visit

    0.24 g

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

2 checks passed
  • Page weight: 883 KiB in 44 requests

    883 KiB

    Your homepage downloads 883 KiB in 44 requests on a phone: scripts 522 KiB (17), images 210 KiB (9) and fonts 87 KiB (3). That is a lean page.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

4 to fixGoogle 9793
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

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

  • 6 images without alt text

    6 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • Headings skip levels

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

1 checks passed
  • 45 automated accessibility rules passed

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

SEO

4 to fixGoogle 9283
  • Title is long (90 characters)

    Your title is 90 characters, so Google will cut it off around 60: “Official Home Page of the Apellis Pharmaceuticals Corporate Site | Apellis Pharmaceuticals”.

  • Meta description is long (279 characters)

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 3 links with vague text

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

  • 42 internal links, 6 external

    The homepage links to 42 pages on apellis.com and 6 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Courageous Science + Compassion”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, WebPage and WebSite.

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

  • No llms.txt

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

Other pages

3 to fix65
  • 1 linked page is broken

    Your homepage links to https://apellis.com/about-us/who-we-are, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 8 pages without a meta description

    https://apellis.com/for-patients, https://apellis.com/about-us/corporate-giving, https://apellis.com/focus-areas, https://apellis.com/focus-areas/geographic-atrophy, https://apellis.com/focus-areas/rare-disease and https://apellis.com/our-products and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 13 pages without an H1

    https://apellis.com/for-patients, https://apellis.com/about-us/corporate-giving, https://apellis.com/our-science/science-of-c3, https://apellis.com/our-science/our-pipeline, https://apellis.com/our-science/clinical-trials and https://apellis.com/focus-areas and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

4 checks passed
  • 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 14 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

    19 of 23 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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 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 195 words

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

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

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn more”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “Join the Team” and “Contact Us”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 3 cookies set on arrival

    3

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

  • 12 other companies contacted

    Loading the homepage contacts 12 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 apellis.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
AWS

Company

Founded
2008
Headquarters
Crestwood

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on apellis.com, including 10 speed issues, 4 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