Website review, no card needed
justrightreader.com website review
Visit site (opens in a new tab)Reviewed 9 November 202629 issues · 77 checks
This review found 29 issues worth fixing on justrightreader.com, 9 of them high impact, across 77 checks. The most urgent: page weight: 18.4 MB in 625 requests. 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
Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.
Show as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.6 s |
| Jul 4, 2026 | 2.7 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.0 s |
| Oct 24, 2026 | 2.1 s |
| Oct 31, 2026 | 2.1 s |
| Nov 7, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 130 ms |
| May 30, 2026 | 134 ms |
| Jun 6, 2026 | 136 ms |
| Jun 13, 2026 | 137 ms |
| Jun 20, 2026 | 141 ms |
| Jun 27, 2026 | 143 ms |
| Jul 4, 2026 | 142 ms |
| Jul 11, 2026 | 136 ms |
| Jul 18, 2026 | 128 ms |
| Jul 25, 2026 | 125 ms |
| Aug 1, 2026 | 119 ms |
| Aug 8, 2026 | 124 ms |
| Aug 15, 2026 | 125 ms |
| Aug 22, 2026 | 125 ms |
| Aug 29, 2026 | 135 ms |
| Sep 5, 2026 | 129 ms |
| Sep 12, 2026 | 137 ms |
| Sep 19, 2026 | 144 ms |
| Sep 26, 2026 | 149 ms |
| Oct 3, 2026 | 159 ms |
| Oct 10, 2026 | 146 ms |
| Oct 17, 2026 | 142 ms |
| Oct 24, 2026 | 140 ms |
| Oct 31, 2026 | 143 ms |
| Nov 7, 2026 | 152 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.6 s
1.2 s
1.8 s
2.5 s
3.1 s
3.7 s
4.3 s
4.9 s
Speed
Main-thread work: 5.6 s
A phone's processor spends 5.6 s on main-thread work while loading, 2.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Vimeo, testimonial.to and ZenDesk and others), adding 13.1 MB and 1.3 s of main-thread time.
Vimeo adds 346 ms
346 msVimeo costs a phone 346 ms of main-thread work and 9.6 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.
testimonial.to adds 218 ms
218 mstestimonial.to costs a phone 218 ms of main-thread work and 553 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 78 ms
78 msShopify costs a phone 78 ms of main-thread work and 1.8 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.
ZenDesk adds 203 ms
203 msZenDesk costs a phone 203 ms of main-thread work and 430 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.
ondigitalocean.app adds 93 ms
93 msondigitalocean.app costs a phone 93 ms of main-thread work and 361 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.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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: 12 ms
12 msYour server sent the HTML in 12 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 14.4 s
14.4 sVisually, the page fills in at 14.4 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 6.1 s
6.1 sThe first text or image appears after 6.1 s on a phone. Good is under 1.8 s.
44 images without width and height
44 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 130 ms to 152 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 161 ms
161 msReal visitors wait 161 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.10
0.10For real visitors the layout shifts by 0.10 (75th percentile). Good is under 0.1.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 409 ms
409 msReal visitors wait 409 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.077
0.077The layout barely moves while loading (CLS 0.077, good is under 0.1).
Images and page weight
Page weight: 18.4 MB in 625 requests
18.4 MBYour homepage downloads 18.4 MB in 625 requests on a phone: other files 9.6 MB (248), scripts 4.9 MB (215) and images 2.2 MB (102). Under 2 MB keeps phones on slow connections fast.
10 images far larger than shown
760 KiB10 images are downloaded at several times the size a phone draws them, for example 072025_Homepage_Graphics_11.png at 1,500 px wide, shown at 65 px. Resized copies would save about 760 KiB.
An image on the first screen is lazy-loaded
JRR_one_line_logo_new.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
4 images below the first screen load straight away
4 images further down the page (300 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 5.2 g of CO₂ per visit
5.20 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.20 g of CO₂e: 624.2 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
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
2 frames have no title, so screen-reader users cannot tell what they contain.
Links must have discernible text (2 elements)
Links must have discernible text: 2 elements on the page fail this check, rated serious by axe-core.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
All page content should be contained by landmarks (50 elements)
All page content should be contained by landmarks: 50 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
16 form fields without a label
16 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 51 images in the HTML carry an alt attribute.
39 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: 39 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (69 characters)
Your title is 69 characters, so Google will cut it off around 60: “Just Right Reader | Data-Driven Phonics Program + Decodable Libraries”.
5 links with vague text
5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
90 internal links, 18 external
The homepage links to 90 pages on justrightreader.com and 18 external pages.
7 checks passed
Meta description: 151 characters
Your meta description is 151 characters: “Accelerate reading achievement with a complete Science of Reading phonics program, data-driven resources, and family en…”.
One H1 headline
Your main headline reads: “Accelerate Reading Achievement”.
Canonical URL set
The canonical URL is https://justrightreader.com/.
Structured data in place
Structured data found: WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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://justrightreader.com/sitemap.xml.
AI search readiness
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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (702 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://justrightreader.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without an H1
https://justrightreader.com/pages/research 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 48 found) and read each the way a search engine does.
6 checks passed
Linked pages load
10 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.
Every page has a meta description
All 10 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.
Every page has a title
All 10 pages that loaded have a <title>.
Best practices
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
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_SOCKET_NOT_CONNECTED”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
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 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 435 words of copy
The homepage carries about 435 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop” and “Shop Program”.
14 calls to action
The homepage has 14 calls to action, for example “Shop”, “Shop Phonics Program” and “Request a Sample”.
1 short form
A short form (1 field at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block and 4 trust badges.
Analytics in place
Analytics detected: Hotjar and HubSpot.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 2 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.
24 cookies set on arrival
24Opening the homepage sets 24 cookies, 7 of them by other companies (measured from a US location before any click).
58 other companies contacted
Loading the homepage contacts 58 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: HubSpot cookie banner
A consent management tool (HubSpot cookie banner) 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 justrightreader.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 10 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pagefly Ai Page Builder · Zepto Product Personalizer · Frequently Bought · Recommenda Quiz Builder · Pop Convert · w3apps.co · amazonaws.com · rechargecdn.com · slicktext.com · hubapi.com
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
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Hotjar
- Hosting
- Shopify
Hiring
- Hiring
- 16 open roles
- Teams
- Sales (5), Production (1)
- Job board
- applicantpro
Company
- Headquarters
- San Francisco
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 justrightreader.com, including 10 speed issues, 2 SEO issues and 1 conversion gap. 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.