Website review, no card needed

schmidtfutures.org logo

schmidtfutures.org website review

Visit site (opens in a new tab)Reviewed 3 November 202647 issues · 87 checks

This review found 47 issues worth fixing on schmidtfutures.org, 20 of them high impact, across 87 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.3 s1.6 sMay 16Oct 312.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.1 s
May 23, 20262.5 s
May 30, 20262.3 s
Jun 6, 20262.0 s
Jun 13, 20262.0 s
Jun 20, 20261.9 s
Jun 27, 20261.9 s
Jul 4, 20261.8 s
Jul 11, 20261.9 s
Jul 18, 20262.1 s
Jul 25, 20262.2 s
Aug 1, 20262.4 s
Aug 8, 20262.5 s
Aug 15, 20262.5 s
Aug 22, 20262.6 s
Aug 29, 20262.6 s
Sep 5, 20262.5 s
Sep 12, 20262.6 s
Sep 19, 20262.5 s
Sep 26, 20262.5 s
Oct 3, 20262.5 s
Oct 10, 20262.5 s
Oct 17, 20262.6 s
Oct 24, 20262.7 s
Oct 31, 20262.7 s
Real-visitor tap response (INP)75th percentile, phones
177 ms109 msMay 16Oct 31153 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026134 ms
May 23, 2026128 ms
May 30, 2026121 ms
Jun 6, 2026125 ms
Jun 13, 2026117 ms
Jun 20, 2026123 ms
Jun 27, 2026125 ms
Jul 4, 2026122 ms
Jul 11, 2026123 ms
Jul 18, 2026133 ms
Jul 25, 2026138 ms
Aug 1, 2026143 ms
Aug 8, 2026149 ms
Aug 15, 2026146 ms
Aug 22, 2026151 ms
Aug 29, 2026158 ms
Sep 5, 2026150 ms
Sep 12, 2026163 ms
Sep 19, 2026169 ms
Sep 26, 2026145 ms
Oct 3, 2026150 ms
Oct 10, 2026145 ms
Oct 17, 2026144 ms
Oct 24, 2026153 ms
Oct 31, 2026153 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 schmidtfutures.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. schmidtfutures.org at 1.1 s1.1 s
  2. schmidtfutures.org at 2.3 s2.3 s
  3. schmidtfutures.org at 3.4 s3.4 s
  4. schmidtfutures.org at 4.5 s4.5 s
  5. schmidtfutures.org at 5.6 s5.6 s
  6. schmidtfutures.org at 6.8 s6.8 s
  7. schmidtfutures.org at 7.9 s7.9 s
  8. schmidtfutures.org at 9.0 s9.0 s

Speed

10 to fix36
  • Improve image delivery

    13.2 s · 4.2 MB

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

  • Mobile performance score: 36

    36/100

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

  • Main-thread work: 7.8 s

    A phone's processor spends 7.8 s on main-thread work while loading, 3.1 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, Google Tag Manager and Crazy Egg and others), adding 6.2 MB and 1.8 s of main-thread time.

  • Google CDN adds 996 ms

    996 ms

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

  • Render-blocking requests

    750 ms

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

  • Reduce unused JavaScript

    705 KiB

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

  • Google Tag Manager adds 509 ms

    509 ms

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

  • imgix adds 0 ms

    0 ms

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

  • 20 long tasks on the main thread

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

  • Font display

    150 ms

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

  • Reduce unused CSS

    59 KiB

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

  • Use efficient cache lifetimes

    6 KiB

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

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

1 checks passed
  • Server response: 4 ms

    4 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 14.3 s

    14.3 s

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

  • Time to Interactive: 15.0 s

    15.0 s

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

  • Total Blocking Time: 1.9 s

    1.9 s

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

  • Speed Index: 6.6 s

    6.6 s

    Visually, the page fills in at 6.6 s (Speed Index). Good is under 3.4 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 CLS: 0.15

    0.15

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

  • Real-user FCP: 2.2 s

    2.2 s

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

  • Real-user TTFB: 1.6 s

    1.6 s

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

  • Cumulative Layout Shift: 0.129

    0.129

    The layout shifts by 0.129 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 5 images without width and height

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

  • Tap response (INP) got 17% slower for real visitors

    +17%

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

  • Largest content (LCP) held steady for real visitors

    -4%

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

2 checks passed
  • Real-user INP: 188 ms

    188 ms

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

  • First Contentful Paint: 1.7 s

    1.7 s

    The first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.

Images and page weight

4 to fix28
  • Page weight: 12.8 MB in 69 requests

    12.8 MB

    Your homepage downloads 12.8 MB in 69 requests on a phone: media 5.7 MB (4), images 5.1 MB (39) and scripts 1.2 MB (10). Under 2 MB keeps phones on slow connections fast.

  • 10 images far larger than shown

    3.7 MB

    10 images are downloaded at several times the size a phone draws them, for example MotifsAcrossMedia_Rock-Art-Panel_Enhanced-scaled.jpg at 2,560 px wide, shown at 350 px. Resized copies would save about 3.7 MB.

  • 3 images over 500 KB

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

  • 2 images below the first screen load straight away

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

  • About 3.6 g of CO₂ per visit

    3.62 g

    By the Sustainable Web Design model, a visit to your homepage emits about 3.62 g of CO₂e: 434.9 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

9 to fixGoogle 8287
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Orphan list items

    Some list items are not inside a list.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 44 images without alt text

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

  • 10 links without text

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

  • 2 form fields without a label

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

  • Headings skip levels

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

1 checks passed
  • 49 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: 49 passed and 9 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 7781
  • No meta description

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

  • Title is short (23 characters)

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

  • 8 links with vague text

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

  • Open Graph partly set

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

  • 58 internal links, 10 external

    The homepage links to 58 pages on schmidtfutures.org and 10 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Bold science, deep and continuous collaborations”.

  • Canonical URL set

    The canonical URL is https://www.schmidtsciences.org/.

  • 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://www.schmidtsciences.org/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://www.schmidtsciences.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.

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 (902 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 15 pages without a meta description

    https://www.schmidtsciences.org/2025-report-reflection, https://www.schmidtsciences.org/about, https://www.schmidtsciences.org/team, https://www.schmidtsciences.org/awardees, https://www.schmidtsciences.org/faq and https://www.schmidtsciences.org/careers and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.schmidtsciences.org/team 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 26 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.

  • 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

3 to fixGoogle 9671
  • 1 broken image

    1 image failed to load on a phone, for example https://www.schmidtsciences.org/.

  • 8 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • 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.

  • A 11-field form

    Your longest form asks for 11 fields (1 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 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 576 words of copy

    The homepage carries about 576 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Sign Up For Our Newsletter”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Sign Up”, “Learn More” and “Apply”.

  • Analytics in place

    Analytics detected: Google Analytics.

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.

  • 8 other companies contacted

    Loading the homepage contacts 8 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 schmidtfutures.org, 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
Tailwind CSS
Analytics
Google Analytics
Hosting
Fastly

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on schmidtfutures.org, including 21 speed issues, 3 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