Website review, no card needed

tutorax.com logo

tutorax.com website review

Visit site (opens in a new tab)Reviewed 4 November 202631 issues · 84 checks

This review found 31 issues worth fixing on tutorax.com, 13 of them high impact, across 84 checks. The most urgent: reduce unused JavaScript. 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.6 s2.3 sMay 16Oct 312.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.5 s
May 23, 20263.4 s
May 30, 20263.3 s
Jun 6, 20263.3 s
Jun 13, 20263.3 s
Jun 20, 20263.2 s
Jun 27, 20263.1 s
Jul 4, 20263.1 s
Jul 11, 20263.0 s
Jul 18, 20262.9 s
Jul 25, 20262.8 s
Aug 1, 20262.6 s
Aug 8, 20262.5 s
Aug 15, 20262.5 s
Aug 22, 20262.5 s
Aug 29, 20262.5 s
Sep 5, 20262.6 s
Sep 12, 20262.5 s
Sep 19, 20262.4 s
Sep 26, 20262.5 s
Oct 3, 20262.5 s
Oct 10, 20262.7 s
Oct 17, 20262.8 s
Oct 24, 20262.8 s
Oct 31, 20262.7 s
Real-visitor tap response (INP)75th percentile, phones
171 ms104 msMay 16Oct 31163 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026113 ms
May 23, 2026112 ms
May 30, 2026112 ms
Jun 6, 2026113 ms
Jun 13, 2026113 ms
Jun 20, 2026114 ms
Jun 27, 2026120 ms
Jul 4, 2026124 ms
Jul 11, 2026128 ms
Jul 18, 2026129 ms
Jul 25, 2026128 ms
Aug 1, 2026127 ms
Aug 8, 2026127 ms
Aug 15, 2026130 ms
Aug 22, 2026137 ms
Aug 29, 2026142 ms
Sep 5, 2026145 ms
Sep 12, 2026148 ms
Sep 19, 2026151 ms
Sep 26, 2026154 ms
Oct 3, 2026155 ms
Oct 10, 2026157 ms
Oct 17, 2026162 ms
Oct 24, 2026163 ms
Oct 31, 2026163 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 tutorax.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

8 to fix49
  • Reduce unused JavaScript

    4.0 s · 773 KiB

    About 773 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.0 s faster on a phone.

  • Render-blocking requests

    4.3 s

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

  • Mobile performance score: 49

    49/100

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

  • 3,931 HTML elements

    The page has 3,931 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Use efficient cache lifetimes

    650 ms · 125 KiB

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

  • Reduce unused CSS

    560 ms · 87 KiB

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

  • Main-thread work: 2.4 s

    A phone's processor spends 2.4 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Google Maps adds 122 ms

    122 ms

    Google Maps costs a phone 122 ms of main-thread work and 340 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Maps, Facebook and ablyft.com and others), adding 511 KiB and 209 ms of main-thread time.

  • 10 long tasks on the main thread

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

  • Improve image delivery

    150 ms · 17 KiB

    1 image could be 17 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • Legacy JavaScript

    21 KiB

    Polyfills for old browsers add 21 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.

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

    Your server sent the HTML in 9 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: 17.1 s

    17.1 s

    Your largest element takes 17.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “LA RÉFÉRENCE EN TUTORAT & SERVICES SPÉCIALISÉS TUTORAT ・ OR…”.

  • Time to Interactive: 17.1 s

    17.1 s

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

  • First Contentful Paint: 4.6 s

    4.6 s

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

  • Speed Index: 6.8 s

    6.8 s

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

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

    +45%

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Total Blocking Time: 443 ms

    443 ms

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

6 checks passed
  • Real-user LCP: 1.9 s

    1.9 s

    Real visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 154 ms

    154 ms

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

  • Real-user TTFB: 417 ms

    417 ms

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

  • Largest content (LCP) got 19% faster for real visitors

    -19%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix85
  • Page weight: 3.1 MB in 164 requests

    3.1 MB

    Your homepage downloads 3.1 MB in 164 requests on a phone: scripts 1.7 MB (61), fonts 518 KiB (9) and other files 454 KiB (19). Under 2 MB keeps phones on slow connections fast.

  • About 0.9 g of CO₂ per visit

    0.87 g

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

5 to fixGoogle 8593
  • 18 text elements with low contrast

    18 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Elements must only use permitted ARIA attributes (8 elements)

    Elements must only use permitted ARIA attributes: 8 elements on the page fail this check, rated serious by axe-core.

  • 6 tap targets too small

    6 tap targets are too small or too close together to hit reliably with a finger.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 6 links without text

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

  • Headings skip levels

    Headings skip levels (h2 → h4, h3 → h5 and h3 → h6), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 26 images in the HTML carry an alt attribute.

  • 51 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 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

Google 100100
  • 356 internal links, 17 external

    The homepage links to 356 pages on tutorax.com and 17 external pages.

8 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “Service de tutorat, d'aide aux devoirs et de soutien scolaire. Des tuteurs qualifiés!(mathématiques, français, science,…”.

  • One H1 headline

    Your main headline reads: “LA RÉFÉRENCE EN TUTORAT & SERVICES SPÉCIALISÉS”.

  • Title: 60 characters

    Your title is a healthy 60 characters: “Tutorax© #1 en Tutorat - Aide aux devoirs - Soutien scolaire”.

  • Canonical URL set

    The canonical URL is https://tutorax.com/.

  • Structured data in place

    Structured data found: EducationalOrganization and 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://tutorax.com/sitemap_index.xml.

AI search readiness

100
4 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: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (4,562 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://tutorax.com/llms.txt (195 KiB, 701 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Other pages

4 to fix81
  • 3 linked pages hidden from search

    https://tutorax.com/inscription, https://tutorax.com/ecoles and https://tutorax.com/tutorat-entreprise-organisme are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 2 pages share a meta description

    https://tutorax.com/ecoles and https://tutorax.com/tutorat-entreprise-organisme use the same meta description. A description written for each page earns more clicks.

  • 3 links to non-canonical URLs

    Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://tutorax.com/aide-aux-devoirs-tutorat-en-ligne, whose canonical is https://tutorax.com/tutorat-en-ligne. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://tutorax.com/inscription 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 86 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 13 small tap targets

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

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix69
  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No analytics detected

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

  • A 53-field form

    Your longest form asks for 53 fields (44 required). Every extra field lowers completion.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 515 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “GET STARTED” and “Get My Child's Plan →”.

  • Social proof on the page

    Social proof on the homepage: 181 testimonial or review blocks and a star rating.

  • Direct contact links

    Visitors can reach you directly: 16 phone links and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

  • 4 trackers load before any consent

    4

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

  • 2 cookies set on arrival

    2

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

  • 16 other companies contacted

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

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) 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 tutorax.com, 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
jQuery
Analytics
Microsoft Clarity
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on tutorax.com, including 16 speed issues and 4 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