Website review, no card needed
brightspirevirtualschool.com website review
Visit site (opens in a new tab)Reviewed 8 November 202632 issues · 80 checks
This review found 32 issues worth fixing on brightspirevirtualschool.com, 11 of them high impact, across 80 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
76C- #72,300 of 118,362 reviewed websitesbeats 34%
- #46,651 of 67,243 online storesbeats 26%
- #44,256 of 61,313 Shopify storesbeats 23%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.2 s |
| May 23, 2026 | 1.2 s |
| May 30, 2026 | 1.1 s |
| Jun 6, 2026 | 1.1 s |
| Jun 13, 2026 | 1.1 s |
| Jun 20, 2026 | 1.2 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.2 s |
| Aug 1, 2026 | 1.3 s |
| Aug 8, 2026 | 1.3 s |
| Aug 15, 2026 | 1.3 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.4 s |
| Oct 31, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 136 ms |
| May 23, 2026 | 130 ms |
| May 30, 2026 | 122 ms |
| Jun 6, 2026 | 136 ms |
| Jun 13, 2026 | 120 ms |
| Jun 20, 2026 | 129 ms |
| Jul 4, 2026 | 120 ms |
| Jul 11, 2026 | 150 ms |
| Jul 18, 2026 | 128 ms |
| Jul 25, 2026 | 128 ms |
| Aug 1, 2026 | 143 ms |
| Aug 8, 2026 | 142 ms |
| Aug 15, 2026 | 163 ms |
| Aug 22, 2026 | 179 ms |
| Aug 29, 2026 | 183 ms |
| Sep 5, 2026 | 188 ms |
| Sep 12, 2026 | 172 ms |
| Sep 19, 2026 | 161 ms |
| Sep 26, 2026 | 152 ms |
| Oct 3, 2026 | 161 ms |
| Oct 10, 2026 | 158 ms |
| Oct 17, 2026 | 159 ms |
| Oct 24, 2026 | 180 ms |
| Oct 31, 2026 | 181 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
How it loaded on a phone
0.5 s
1.1 s
1.6 s
2.2 s
2.7 s
3.3 s
3.8 s
4.4 s
Speed
Reduce unused JavaScript
2.4 s · 726 KiBAbout 726 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.
Use efficient cache lifetimes
1.1 s · 560 KiB22 files are served with short cache lifetimes, so returning visitors download them again (560 KiB).
Mobile performance score: 61
61/100Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Optanon, Shopify and Klaviyo and others), adding 1.5 MB and 673 ms of main-thread time.
Main-thread work: 3.4 s
A phone's processor spends 3.4 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Optanon adds 225 ms
225 msOptanon costs a phone 225 ms of main-thread work and 296 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.
Shopify adds 135 ms
135 msShopify costs a phone 135 ms of main-thread work and 753 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.
1,760 HTML elements
The page has 1,760 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
250 ms · 213 KiB6 images could be 213 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.
Legacy JavaScript
150 ms · 35 KiBPolyfills for old browsers add 35 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 171 ms. During a long task the page ignores taps.
Render-blocking requests
150 ms9 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.
Reduce unused CSS
33 KiBAbout 33 KiB of CSS is downloaded but never applied on this page.
Duplicated JavaScript
8 KiB8 KiB JavaScript is shipped twice across bundles.
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: 9 ms
9 msYour server sent the HTML in 9 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.4 s
14.4 sYour largest element takes 14.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 18.4 s
18.4 sThe page becomes fully interactive after 18.4 s. Good is under 3.8 s.
Speed Index: 8.4 s
8.4 sVisually, the page fills in at 8.4 s (Speed Index). Good is under 3.4 s.
Real-user INP: 219 ms
219 msReal visitors wait 219 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 36% slower for real visitors
+36%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 136 ms to 181 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 23% slower for real visitors
+23%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.2 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
6 checks passed
Real-user LCP: 1.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.07
0.07For real visitors the layout shifts by 0.07 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 481 ms
481 msReal visitors wait 481 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.073
0.073The layout barely moves while loading (CLS 0.073, good is under 0.1).
Total Blocking Time: 103 ms
103 msScripts block the page for only 103 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.7 MB in 369 requests
3.7 MBYour homepage downloads 3.7 MB in 369 requests on a phone: scripts 1.6 MB (146), other files 1,009 KiB (175) and fonts 569 KiB (6). Under 2 MB keeps phones on slow connections fast.
About 1.0 g of CO₂ per visit
1.04 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.04 g of CO₂e: 124.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
15 text elements with low contrast
15 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 1 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (11 characters)
Your title is only 11 characters: “Brightspire”. Between 30 and 65 characters leaves room to say what you do and for whom.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
One H1 headline
Your <h1> is empty.
46 internal links, 18 external
The homepage links to 46 pages on brightspirevirtualschool.com and 18 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://brightspirevirtualschool.com/.
Structured data in place
Structured data found: Organization 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://brightspirevirtualschool.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://brightspirevirtualschool.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.
3 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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,183 words), so crawlers that don't run JavaScript still read it.
Other pages
3 pages without a meta description
https://brightspirevirtualschool.com/pages/brightspire-in-action, https://brightspirevirtualschool.com/pages/middle-school-curriculum and https://brightspirevirtualschool.com/pages/high-school-curriculum have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages without an H1
https://brightspirevirtualschool.com/pages/career-and-technical-virtual-high-school-single-courses, https://brightspirevirtualschool.com/pages/brightspire-in-action, https://brightspirevirtualschool.com/pages/high-school-curriculum and https://brightspirevirtualschool.com/pages/devry-early-college-credit 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 24 found) and read each the way a search engine does.
5 checks passed
Linked pages load
5 pages of 15 loaded without an error (the rest turned automated requests away).
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 5 pages that loaded have a <title>.
Best practices
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Unexpected token '*'”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
16 of 17 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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 649 words of copy
The homepage carries about 649 words of visible text.
2 checks passed
6 calls to action
The homepage has 6 calls to action, for example “Start an application”, “Learn More” and “Apply Now”.
5 short forms
5 short forms (1 field at most) are right on the homepage.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Klaviyo (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
14 cookies set on arrival
14Opening the homepage sets 14 cookies, 1 of them by other companies (measured from a US location before any click).
30 other companies contacted
Loading the homepage contacts 30 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
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 brightspirevirtualschool.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 7 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Onetrust Consent Management · Klaviyo Email Marketing Sms · Inbox · Stape Remix · Forms · cloudfront.net · loox.io
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on brightspirevirtualschool.com, including 16 speed issues, 5 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.