Programmable

Website review, no card needed

starfall.com logo

starfall.com website review

Visit site (opens in a new tab)Reviewed 11 October 202629 issues · 74 checks

This review found 29 issues worth fixing on starfall.com, 6 of them high impact, across 74 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

Site score

86B

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
1.3 s1.2 sApr 18Oct 31.2 s
Show as table
DateReal-visitor load time (LCP)
Apr 18, 20261.2 s
Apr 25, 20261.2 s
May 2, 20261.2 s
May 30, 20261.2 s
Jun 6, 20261.2 s
Jun 13, 20261.2 s
Jun 20, 20261.2 s
Jun 27, 20261.2 s
Jul 4, 20261.3 s
Jul 11, 20261.3 s
Jul 18, 20261.3 s
Jul 25, 20261.3 s
Aug 1, 20261.3 s
Aug 8, 20261.3 s
Aug 15, 20261.3 s
Aug 22, 20261.3 s
Aug 29, 20261.3 s
Sep 5, 20261.2 s
Sep 12, 20261.2 s
Sep 19, 20261.2 s
Sep 26, 20261.2 s
Oct 3, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
108 ms99 msApr 18Oct 3104 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 2026103 ms
Apr 25, 2026103 ms
May 2, 2026103 ms
Jun 6, 2026100 ms
Jun 13, 2026101 ms
Jun 20, 2026103 ms
Jun 27, 2026104 ms
Jul 4, 2026105 ms
Jul 11, 2026105 ms
Jul 18, 2026106 ms
Jul 25, 2026107 ms
Aug 1, 2026107 ms
Aug 8, 2026107 ms
Aug 15, 2026105 ms
Aug 22, 2026105 ms
Aug 29, 2026104 ms
Sep 5, 2026103 ms
Sep 12, 2026104 ms
Sep 19, 2026104 ms
Sep 26, 2026105 ms
Oct 3, 2026104 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

www.starfall.com (opens in a new tab)
Full-page screenshot of starfall.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

5 to fix74

  • Improve image delivery

    2.3 s · 666 KiB

    14 images could be 666 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.3 s faster on a phone.

  • Render-blocking requests

    2.2 s

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

  • Use efficient cache lifetimes

    1.6 s · 282 KiB

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

  • Mobile performance score: 74

    74/100

    Your mobile performance score is 74 (desktop: 90). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    300 ms · 58 KiB

    About 58 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Font display

    200 ms

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

  • Document request latency

    49 KiB

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

  • Reduce unused CSS

    29 KiB

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

  • Minify CSS

    24 KiB

    24 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

    2 KiB

    2 KiB could be saved by minifying JavaScript.

2 checks passed

  • Main-thread work: 0.2 s

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

  • Server response: 141 ms

    141 ms

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

Core Web Vitals

8 to fix100

  • 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: 5.1 s

    5.1 s

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • Speed Index: 4.7 s

    4.7 s

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

  • Time to Interactive: 5.1 s

    5.1 s

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

  • 13 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +1%

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

  • Largest content (LCP) held steady for real visitors

    +3%

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

5 checks passed

  • Real-user LCP: 2.2 s

    2.2 s

    Real visitors wait 2.2 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.00

    0.00

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

2 to fix80

  • 12 images in older formats

    12 images (737 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.

  • 9 images far larger than shown

    387 KiB

    9 images are downloaded at several times the size a phone draws them, for example grades45.png at 660 px wide, shown at 165 px. Resized copies would save about 387 KiB.

  • 5 images below the first screen load straight away

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

  • About 0.4 g of CO₂ per visit

    0.35 g

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

1 checks passed

  • Page weight: 1.2 MB in 34 requests

    1.2 MB

    Your homepage downloads 1.2 MB in 34 requests on a phone: images 892 KiB (22), fonts 197 KiB (2) and scripts 85 KiB (3). That is a lean page.

Accessibility

Google 100100
2 checks passed

  • Every image has alt text

    All 33 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

6 to fixGoogle 9275

  • Title is long (71 characters)

    Your title is 71 characters, so Google will cut it off around 60: “Starfall Education: Kids Games, Movies, Books & Music for K-5 and above”.

  • No structured data

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

  • Meta description is long (169 characters)

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

  • 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 XML sitemap

    No XML sitemap at https://www.starfall.com/sitemap.txt, so Google discovers your pages only by following links.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

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

  • 11 internal links, 25 external

    The homepage links to 11 pages on starfall.com and 25 external pages.

3 checks passed

  • One H1 headline

    Your main headline reads: “Starfall Grades”.

  • Canonical URL set

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

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

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

Other pages

4 to fix73

  • 1 page points its canonical at the homepage

    https://www.starfall.com/h/index.php declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 pages share a title

    https://www.starfall.com/h and https://www.starfall.com/h/index.php all use the title “Starfall Education: Kids Games, Movies, Books & Music for K-5 and abo…”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages without a meta description

    https://www.starfall.com/h/accessibility.php, https://www.starfall.com/h/fun-to-read and https://www.starfall.com/h/im-reading have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://www.starfall.com/h/fun-to-read and https://www.starfall.com/h/im-reading have no <h1> headline, so visitors and search engines get no clear main topic.

  • 6 pages with very little text

    https://www.starfall.com/h/index-kindergarten.php, https://www.starfall.com/h/index-grades123.php, https://www.starfall.com/h/index-grades45.php, https://www.starfall.com/h/abcs, https://www.starfall.com/h/fun-to-read and https://www.starfall.com/h/im-reading have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 9 internal pages checked

    We fetched 9 pages linked from your homepage and read each the way a search engine does.

3 checks passed

  • Linked pages load

    All 9 pages we checked loaded without an error.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 9 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

    12 of 14 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75

  • Thin social proof

    Social proof on the homepage: 16 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

    The homepage carries about 496 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: “How to Join”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “How to Join” and “Contact”.

  • 1 short form

    A short form (0 fields at most) is right on the homepage.

Privacy and tracking

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

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

Upkeep, stack and company

Company

Founded
2002
Headquarters
Boulder

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on starfall.com, including 13 speed issues, 6 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