Website review, no card needed

irvinesci.com logo

irvinesci.com website review

Visit site (opens in a new tab)Reviewed 4 November 202643 issues · 88 checks

This review found 43 issues worth fixing on irvinesci.com, 14 of them high impact, across 88 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
3.7 s2.4 sMay 16Oct 312.9 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.8 s
May 23, 20262.9 s
May 30, 20263.0 s
Jun 6, 20263.0 s
Jun 13, 20262.9 s
Jun 20, 20262.8 s
Jun 27, 20262.8 s
Jul 4, 20262.9 s
Jul 11, 20263.0 s
Jul 18, 20263.1 s
Jul 25, 20262.9 s
Aug 1, 20262.8 s
Aug 8, 20262.5 s
Aug 15, 20262.5 s
Aug 22, 20262.8 s
Aug 29, 20262.8 s
Sep 5, 20262.9 s
Sep 12, 20262.8 s
Sep 19, 20263.4 s
Sep 26, 20263.6 s
Oct 3, 20263.5 s
Oct 10, 20263.5 s
Oct 17, 20262.9 s
Oct 24, 20263.0 s
Oct 31, 20262.9 s
Real-visitor tap response (INP)75th percentile, phones
122 ms83 msMay 16Oct 3195 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026102 ms
May 23, 2026105 ms
May 30, 2026101 ms
Jun 6, 202696 ms
Jun 13, 202691 ms
Jun 20, 202688 ms
Jun 27, 202690 ms
Jul 4, 202696 ms
Jul 11, 2026102 ms
Jul 18, 2026102 ms
Jul 25, 202697 ms
Aug 1, 202693 ms
Aug 8, 202687 ms
Aug 15, 202691 ms
Aug 22, 2026105 ms
Aug 29, 2026108 ms
Sep 5, 2026112 ms
Sep 12, 2026115 ms
Sep 19, 2026113 ms
Sep 26, 2026117 ms
Oct 3, 2026114 ms
Oct 10, 2026106 ms
Oct 17, 202696 ms
Oct 24, 202695 ms
Oct 31, 202695 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 irvinesci.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. irvinesci.com at 0.7 s0.7 s
  2. irvinesci.com at 1.4 s1.4 s
  3. irvinesci.com at 2.0 s2.0 s
  4. irvinesci.com at 2.7 s2.7 s
  5. irvinesci.com at 3.4 s3.4 s
  6. irvinesci.com at 4.1 s4.1 s
  7. irvinesci.com at 4.8 s4.8 s
  8. irvinesci.com at 5.5 s5.5 s

Speed

10 to fix50
  • Render-blocking requests

    2.0 s

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

  • Main-thread work: 6.0 s

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

  • Improve image delivery

    650 ms · 1.7 MB

    21 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.

  • Reduce unused CSS

    870 ms · 142 KiB

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

  • Mobile performance score: 50

    50/100

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google CDN, New Relic and Other Google APIs/SDKs and others), adding 1.3 MB and 731 ms of main-thread time.

  • Reduce unused JavaScript

    566 KiB

    About 566 KiB of JavaScript is downloaded but never used on this page.

  • Google CDN adds 368 ms

    368 ms

    Google CDN costs a phone 368 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.

  • 13 long tasks on the main thread

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

  • New Relic adds 282 ms

    282 ms

    New Relic costs a phone 282 ms of main-thread work and 24 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

    150 ms · 3 KiB

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

  • Document request latency

    151 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Font display

    150 ms

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

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 32 ms

    32 ms

    Your server sent the HTML in 32 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.

  • Largest Contentful Paint: 16.7 s

    16.7 s

    Your largest element takes 16.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Download Brochure”.

  • Time to Interactive: 23.3 s

    23.3 s

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

  • Speed Index: 10.7 s

    10.7 s

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

  • First Contentful Paint: 3.5 s

    3.5 s

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

  • Real-user LCP: 2.9 s

    2.9 s

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

  • Real-user FCP: 2.6 s

    2.6 s

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

  • Real-user TTFB: 1.7 s

    1.7 s

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

  • Total Blocking Time: 375 ms

    375 ms

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

  • 9 images without width and height

    9 images 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-31, real Chrome visitors' tap response (inp) went from 102 ms to 95 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    +2%

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

3 checks passed
  • Real-user INP: 95 ms

    95 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Cumulative Layout Shift: 0.014

    0.014

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

Images and page weight

3 to fix45
  • Page weight: 5.6 MB in 345 requests

    5.6 MB

    Your homepage downloads 5.6 MB in 345 requests on a phone: images 2.5 MB (29), scripts 1.6 MB (269) and other files 726 KiB (18). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    Screen_Shot_2025-05-19_at_8.24.05_AM.png weighs 684 KiB. On a phone connection a single image that size takes seconds.

  • 7 images far larger than shown

    305 KiB

    7 images are downloaded at several times the size a phone draws them, for example disease-modelling-illustrations-0926-01.png at 1,200 px wide, shown at 330 px. Resized copies would save about 305 KiB.

  • 5 images below the first screen load straight away

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

  • About 1.6 g of CO₂ per visit

    1.58 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

7 to fixGoogle 8490
  • 27 text elements with low contrast

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

  • 23 tap targets too small

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

  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

    All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

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

  • 4 links without text

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

  • 3 form fields without a label

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 41 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

5 to fixGoogle 8380
  • Title is short (4 characters)

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

  • 26 links with vague text

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

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Structured data has 1 problem

    Structured data found (WebSite) but with 1 problem, for example “WebSite: missing name”.

  • 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 X (Twitter) card tag

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

  • 182 internal links, 2 external

    The homepage links to 182 pages on irvinesci.com and 2 external pages.

4 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “FUJIFILM Biosciences is a global life sciences and medical media provider with an array of innovative products to assis…”.

  • One H1 headline

    Your main headline reads: “Home Page”.

  • 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://fujifilmbiosciences.fujifilm.com/media/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.

  • No llms.txt

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

Other pages

4 to fix55
  • 2 linked pages are broken

    Your homepage links to https://fujifilmbiosciences.fujifilm.com/website-downtime-sap-launch and https://fujifilmbiosciences.fujifilm.com/ransomware-notice, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 2 pages without a title

    https://fujifilmbiosciences.fujifilm.com/us/subscribe and https://fujifilmbiosciences.fujifilm.com/subscribe have no <title>, so Google invents the link text in results.

  • 13 pages share a meta description

    https://fujifilmbiosciences.fujifilm.com/us/privacy-policy, https://fujifilmbiosciences.fujifilm.com/ccpa-cpra-notice-of-right-to-opt-out, https://fujifilmbiosciences.fujifilm.com/us/subscribe, https://fujifilmbiosciences.fujifilm.com/subscribe, https://fujifilmbiosciences.fujifilm.com/us/applications/bioprocessing.html and https://fujifilmbiosciences.fujifilm.com/us/applications/cell-therapy-solutions.html and 7 others use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://fujifilmbiosciences.fujifilm.com/ccpa-cpra-notice-of-right-to-opt-out has 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 76 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.

  • Every page has a meta description

    All 13 pages that loaded have a meta description.

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

Best practices

1 to fixGoogle 9693
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “MktoForms2 is not defined”.

2 checks passed
  • Tap targets are thumb-sized

    66 of 74 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

    Social proof on the homepage: 2 customer or partner logos. 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.

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

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

4 checks passed
  • Clear next step on the first screen

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

  • 25 calls to action

    The homepage has 25 calls to action, for example “Learn more”, “Join Our Mailing List Today!” and “Learn More”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

Privacy and tracking

  • 16 cookies set on arrival

    16

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

  • 7 other companies contacted

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

Upkeep, stack and company

Stack

E-commerce
Magento
Analytics
Google Tag Manager
Hosting
Fastly

Hiring

Hiring
100 open roles
Job board
icims

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on irvinesci.com, including 20 speed issues, 5 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