lji.org website review

1 image could be 2.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 14.3 s faster on a phone.

About 3.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 8.3 s faster on a phone.

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

About 696 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 3.0 s faster on a phone.

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

classy.org costs a phone 1.6 s of main-thread work and 2.1 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

Your mobile performance score is 27. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

8 third-party services load with your homepage (classy.org, YouTube and PayPal and others), adding 6.3 MB and 4.5 s of main-thread time.

YouTube costs a phone 906 ms of main-thread work and 2.0 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.

PayPal costs a phone 628 ms of main-thread work and 1.0 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.

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

Reduce initial server response time. Google estimates savings of 543 ms on a phone.

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

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

38 KiB could be saved by minifying CSS.

rum-ingress-coralogix.com costs a phone 309 ms of main-thread work and 77 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.

The page has 1,610 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Your server takes 643 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

Polyfills for old browsers add 23 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

13 KiB could be saved by minifying JavaScript.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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 visitors see the first content after 4.5 s (75th percentile). Good is under 1.8 s.

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

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

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

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

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

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

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

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

Your homepage downloads 15.8 MB in 327 requests on a phone: scripts 8.6 MB (116), images 3.7 MB (28) and HTML 1.0 MB (17). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example Charity-Navigator-Four-Star-Rating-Badge-Full-Color-768x768. at 390 px wide, shown at 92 px. Resized copies would save about 95 KiB.

3 images (317 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.

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

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

Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.

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

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

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

Your title is 104 characters, so Google will cut it off around 60: “La Jolla Institute for Immunology – Our breakthroughs in immunology make Life Without Dis…”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

There is no robots.txt at lji.org/robots.txt, the first file search crawlers ask for.

Open Graph is missing og:title and og:description, so shared links fall back to guesses.

The homepage links to 209 pages on lji.org and 52 external pages.

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.

There is no https://www.lji.org/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.

https://www.lji.org/research, https://www.lji.org/databases, https://www.lji.org/research/database-of-immune-cell-epigenomics, https://www.lji.org/research/immune-epitope-database, https://www.lji.org/research/diseases and https://www.lji.org/research/licensing-opportunities and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.lji.org/research, https://www.lji.org/databases, https://www.lji.org/research/database-of-immune-cell-epigenomics, https://www.lji.org/research/immune-epitope-database, https://www.lji.org/research/diseases and https://www.lji.org/research/licensing-opportunities and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.lji.org/research/database-of-immune-cell-epigenomics, https://www.lji.org/research/immune-epitope-database, https://www.lji.org/research/diseases, https://www.lji.org/research/licensing-opportunities, https://www.lji.org/research/research-centers/center-for-sex-based-differences-in-the-immune-system and https://www.lji.org/research/research-centers/center-for-vaccine-innovation took over 3 s to send their HTML from our server.

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

8 of 18 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

6 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

Chrome logged issues while loading the page (“Cookie”).

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

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.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.

Opening the homepage sets 13 cookies, 1 of them by other companies (measured from a US location before any click).

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.

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