Website review, no card needed

3plearning.com logo

3plearning.com website review

Visit site (opens in a new tab)Reviewed 26 October 202632 issues · 100 checks

This review found 32 issues worth fixing on 3plearning.com, 7 of them high impact, across 100 checks. The most urgent: render-blocking requests. 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.5 s3.1 sMay 2Oct 173.4 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.2 s
May 9, 20263.2 s
May 16, 20263.3 s
May 23, 20263.4 s
May 30, 20263.3 s
Jun 6, 20263.3 s
Jun 13, 20263.4 s
Jun 20, 20263.4 s
Jun 27, 20263.4 s
Jul 4, 20263.4 s
Jul 11, 20263.4 s
Jul 18, 20263.3 s
Jul 25, 20263.4 s
Aug 1, 20263.4 s
Aug 8, 20263.4 s
Aug 15, 20263.4 s
Aug 22, 20263.4 s
Aug 29, 20263.4 s
Sep 5, 20263.4 s
Sep 12, 20263.3 s
Sep 19, 20263.2 s
Sep 26, 20263.2 s
Oct 3, 20263.2 s
Oct 10, 20263.3 s
Oct 17, 20263.4 s
Real-visitor tap response (INP)75th percentile, phones
190 ms123 msMay 2Oct 17179 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026158 ms
May 9, 2026155 ms
May 16, 2026154 ms
May 23, 2026147 ms
May 30, 2026153 ms
Jun 6, 2026155 ms
Jun 13, 2026151 ms
Jun 20, 2026156 ms
Jun 27, 2026148 ms
Jul 4, 2026145 ms
Jul 11, 2026140 ms
Jul 18, 2026136 ms
Jul 25, 2026135 ms
Aug 1, 2026131 ms
Aug 8, 2026139 ms
Aug 15, 2026145 ms
Aug 22, 2026151 ms
Aug 29, 2026162 ms
Sep 5, 2026161 ms
Sep 12, 2026170 ms
Sep 19, 2026171 ms
Sep 26, 2026165 ms
Oct 3, 2026179 ms
Oct 10, 2026182 ms
Oct 17, 2026179 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

Live view · interaction off

Speed

7 to fix78
  • Render-blocking requests

    2.7 s

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

  • Use efficient cache lifetimes

    650 ms · 1.5 MB

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

  • Mobile performance score: 78

    78/100

    Your mobile performance score is 78 (desktop: 73). 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 (Google Tag Manager, Facebook and Wistia and others), adding 1,018 KiB and 842 ms of main-thread time.

  • Improve image delivery

    635 KiB

    3 images could be 635 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused JavaScript

    150 ms · 428 KiB

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

  • Google Tag Manager adds 322 ms

    322 ms

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

  • 7 long tasks on the main thread

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

  • Reduce unused CSS

    150 ms · 21 KiB

    About 21 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Font display

    50 ms

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

  • Minify JavaScript

    13 KiB

    13 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    12 KiB

    Polyfills for old browsers add 12 KiB JavaScript that modern phones do not need.

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.8 s

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

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

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

  • Time to Interactive: 14.5 s

    14.5 s

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

  • Largest Contentful Paint: 4.0 s

    4.0 s

    Your largest element takes 4.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “3p-header-blended-teaching-software”.

  • Real-user FCP: 1.8 s

    1.8 s

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • Speed Index: 4.3 s

    4.3 s

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

  • Total Blocking Time: 212 ms

    212 ms

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

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

    +15%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 158 ms to 179 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-17, real Chrome visitors' largest content (lcp) went from 3.2 s to 3.4 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: 194 ms

    194 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user TTFB: 599 ms

    599 ms

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

  • Cumulative Layout Shift: 0.007

    0.007

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

Images and page weight

4 to fix58
  • Page weight: 2.5 MB in 132 requests

    2.5 MB

    Your homepage downloads 2.5 MB in 132 requests on a phone: scripts 1.2 MB (38), images 1.1 MB (51) and other files 68 KiB (34). Under 2 MB keeps phones on slow connections fast.

  • 4 images in older formats

    4 images (754 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.

  • 7 images below the first screen load straight away

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

  • 1 image far larger than shown

    44 KiB

    1 image is downloaded at several times the size a phone draws it, for example Mathseeds-ESSA-Badge-1.png at 390 px wide, shown at 48 px. Resized copies would save about 44 KiB.

  • About 0.7 g of CO₂ per visit

    0.72 g

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

Accessibility

4 to fixGoogle 7992
  • Orphan list items

    Some list items are not inside a list.

  • 7 images without alt text

    7 images have no alt text, which hurts accessibility and image search.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  • 8 links without text

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

1 checks passed
  • 35 automated accessibility rules passed

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

SEO

3 to fixGoogle 8591
  • Structured data has 3 problems

    Structured data found (BreadcrumbList, ImageObject, Organization and WebPage) but with 3 problems, for example “WebPage: thumbnailUrl is not an absolute URL ("/wp-content/uploads/2020/10/3p-header-blended-teachi…”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 6 links with vague text

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

  • 110 internal links, 20 external

    The homepage links to 110 pages on 3plearning.com and 20 external pages.

6 checks passed
  • Meta description: 106 characters

    Your meta description is 106 characters: “3P Learning is a world leading educational software company with a mission to create better ways to learn.”.

  • One H1 headline

    Your main headline reads: “Discover a better way for children to learn”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “3P Learning | Educational teaching software for class and home”.

  • Canonical URL set

    The canonical URL is https://www.3plearning.com/.

  • 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.3plearning.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

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

Other pages

1 to fix95
  • 5 pages without a meta description

    /giving-back, /software/writing-legends, /software/brightpath, /software/literacyplanet and /packages/better-ways-to-learn-maths have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

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

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

2 to fixGoogle 7387
  • 2 small tap targets

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

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Access to font at 'https://assets-homepages-learning.3plearning.net/wp-content/themes/3plearning/fonts/proxima-nova/Pro…”.

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

2 to fix81
  • 1 insecure resource on an https page

    1 resource load over plain http on your https page (for example http://7315551.collect.igodigital.com/collect.js); browsers block or warn about them.

  • No Content-Security-Policy

    No Content-Security-Policy header, the main browser-side defence against injected scripts.

  • No clickjacking protection

    Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

  • No X-Content-Type-Options

    X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

  • 3 links through redirect chains

    3 links go through two or more redirects, for example https://www.3plearning.com/software/3plearning/purchase/.

  • No Referrer-Policy

    No Referrer-Policy header, so full URLs can leak to the sites you link to.

  • No Permissions-Policy

    No Permissions-Policy header to switch off camera, microphone and location for embedded content.

  • No security.txt

    There is no /.well-known/security.txt telling researchers how to report a security problem to you.

6 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (3plearning.com).

  • Valid certificate (88 days left)

    The certificate from Google Trust Services · WE1 verifies for 3plearning.com and is valid for another 88 days.

  • HSTS enabled

    Strict-Transport-Security is set, so browsers always use https.

  • http:// redirects to https

    http://3plearning.com redirects to the secure version.

  • HTTP/2 and HTTP/3

    The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.

  • All 56 links work

    All 56 links checked from your homepage (40 internal, 16 external) answered without errors; 1 did not answer within 5 s.

Domain and trust

  • DNSSEC is off

    3plearning.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

3 checks passed
  • Domain is 20 years old

    20 years

    3plearning.com was registered in Oct 2006 through GoDaddy.com, LLC. An established domain carries more trust with email providers and search engines.

  • Certificate issuers are restricted

    CAA records allow only amazon.com, amazontrust.com, awstrust.com and amazonaws.com to issue certificates for 3plearning.com, so a mis-issued certificate from anyone else is refused.

  • Registered until Oct 2031

    3plearning.com is registered until Oct 2031.

Content and conversion

2 to fix80
  • Thin social proof

    Social proof on the homepage: 7 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 420 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: “Learn more” and “Try for free”.

  • 17 calls to action

    The homepage has 17 calls to action, for example “Free Trial”, “Learn more” and “Try for free”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Email authentication

90
  • Email authentication score: 90/100

    Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

3 checks passed
  • DMARC policy: quarantine

    DMARC tells receivers to quarantine mail that fails authentication, and sends you reports.

  • SPF with a strict ending (-all)

    An SPF record lists your sending servers and tells receivers to reject anything else: “v=spf1 include:spf.protection.outlook.com exists:%{i}._spf.mta.salesforce.com include:sendgrid.net include:_spf.alcheme…”.

  • DKIM signing found

    A DKIM key is published (selector “selector1”, “selector2” and “k1”), so receivers can verify mail really came from you.

Privacy and tracking

  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 3 mores (measured from a US location before any click). A consent tool (Usercentrics) is installed; check it blocks these until visitors agree where the law requires it.

  • 16 cookies set on arrival

    16

    Opening the homepage sets 16 cookies (measured from a US location before any click).

  • 27 other companies contacted

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

1 checks passed
  • Consent tool: Usercentrics

    A consent management tool (Usercentrics) loads with the page.

Upkeep, stack and company

  • It runs WordPress 3.7.1; the current release is 7.1.3.

Stack

CMS
WordPress 3.7.1
Framework
jQuery
Analytics
Google Tag Manager

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 3plearning.com, including 14 speed issues, 3 SEO issues and 2 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