Website review, no card needed
aliancafrancesa.com.br website review
Visit site (opens in a new tab)Reviewed 1 November 202641 issues · 81 checks
This review found 41 issues worth fixing on aliancafrancesa.com.br, 18 of them high impact, across 81 checks. The most urgent: use efficient cache lifetimes. 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
68D- #108,884 of 124,112 reviewed websitesbeats 10%
- #65,033 of 69,786 online storesbeats 5%
- #2,442 of 2,905 WooCommerce storesbeats 13%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.6 s |
| May 16, 2026 | 2.6 s |
| May 23, 2026 | 2.6 s |
| May 30, 2026 | 2.6 s |
| Jun 6, 2026 | 2.6 s |
| Jun 13, 2026 | 2.6 s |
| Jun 20, 2026 | 2.7 s |
| Jun 27, 2026 | 2.7 s |
| Jul 4, 2026 | 2.7 s |
| Jul 11, 2026 | 2.7 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.7 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 2.9 s |
| Aug 22, 2026 | 3.0 s |
| Aug 29, 2026 | 3.0 s |
| Sep 5, 2026 | 2.9 s |
| Sep 12, 2026 | 2.9 s |
| Sep 19, 2026 | 2.9 s |
| Sep 26, 2026 | 2.9 s |
| Oct 3, 2026 | 2.9 s |
| Oct 10, 2026 | 2.9 s |
| Oct 17, 2026 | 3.0 s |
| Oct 24, 2026 | 3.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 149 ms |
| May 16, 2026 | 147 ms |
| May 23, 2026 | 145 ms |
| May 30, 2026 | 142 ms |
| Jun 6, 2026 | 142 ms |
| Jun 13, 2026 | 144 ms |
| Jun 20, 2026 | 153 ms |
| Jun 27, 2026 | 158 ms |
| Jul 4, 2026 | 169 ms |
| Jul 11, 2026 | 174 ms |
| Jul 18, 2026 | 174 ms |
| Jul 25, 2026 | 183 ms |
| Aug 1, 2026 | 182 ms |
| Aug 8, 2026 | 185 ms |
| Aug 15, 2026 | 193 ms |
| Aug 22, 2026 | 194 ms |
| Aug 29, 2026 | 197 ms |
| Sep 5, 2026 | 198 ms |
| Sep 12, 2026 | 197 ms |
| Sep 19, 2026 | 207 ms |
| Sep 26, 2026 | 211 ms |
| Oct 3, 2026 | 214 ms |
| Oct 10, 2026 | 220 ms |
| Oct 17, 2026 | 221 ms |
| Oct 24, 2026 | 231 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
2.7 s
5.5 s
8.2 s
11.0 s
13.7 s
16.5 s
19.2 s
21.9 s
Speed
Use efficient cache lifetimes
4.9 s · 2.8 MB34 files are served with short cache lifetimes, so returning visitors download them again (2.8 MB).
Reduce unused JavaScript
5.5 s · 1.3 MBAbout 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.5 s faster on a phone.
Render-blocking requests
4.2 s89 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.2 s.
Mobile performance score: 43
43/100Your mobile performance score is 43. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.3 s
A phone's processor spends 4.3 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
600 ms · 1.1 MB10 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Google CDN and Facebook and others), adding 2.2 MB and 1.4 s of main-thread time.
Reduce unused CSS
600 ms · 111 KiBAbout 111 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Google Tag Manager adds 470 ms
470 msGoogle Tag Manager costs a phone 470 ms of main-thread work and 718 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.
Google CDN adds 410 ms
410 msGoogle CDN costs a phone 410 ms of main-thread work and 739 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.
Legacy JavaScript
300 ms · 39 KiBPolyfills for old browsers add 39 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
1,507 HTML elements
The page has 1,507 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
19 long tasks on the main thread
19 long tasks block the main thread while loading, the longest for 146 ms. During a long task the page ignores taps.
Minify JavaScript
23 KiB23 KiB could be saved by minifying JavaScript.
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.
1 checks passed
Server response: 144 ms
144 msYour server sent the HTML in 144 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.
Real-user TTFB: 1.9 s
1.9 sReal visitors wait 1.9 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 21.0 s
21.0 sYour largest element takes 21.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Prancheta 1 copiar”. Most of its time is resource load delay (9.6 s).
Speed Index: 20.8 s
20.8 sVisually, the page fills in at 20.8 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 35.5 s
35.5 sThe page becomes fully interactive after 35.5 s. Good is under 3.8 s.
First Contentful Paint: 5.0 s
5.0 sThe first text or image appears after 5.0 s on a phone. Good is under 1.8 s.
Real-user LCP: 3.3 s
3.3 sReal visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 222 ms
222 msReal visitors wait 222 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 53% slower for real visitors
+53%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 149 ms to 231 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.8 s
2.8 sReal visitors see the first content after 2.8 s (75th percentile). Good is under 1.8 s.
Total Blocking Time: 487 ms
487 msScripts block taps and scrolling for 487 ms in total while the page loads. Good is under 200 ms.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) got 18% slower for real visitors
+18%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.6 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.06
0.06For real visitors the layout shifts by 0.06 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.06
0.06The layout barely moves while loading (CLS 0.06, good is under 0.1).
Images and page weight
Page weight: 6.2 MB in 215 requests
6.2 MBYour homepage downloads 6.2 MB in 215 requests on a phone: scripts 2.5 MB (85), images 1.9 MB (31) and fonts 984 KiB (11). Under 2 MB keeps phones on slow connections fast.
About 1.8 g of CO₂ per visit
1.76 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.76 g of CO₂e: 211.3 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
14 tap targets too small
14 tap targets are too small or too close together to hit reliably with a finger.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (27 elements)
All page content should be contained by landmarks: 27 elements on the page fail this check, rated moderate by axe-core.
3 form fields without a label
3 form fields have 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. (2 elements).
1 checks passed
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 4 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
5 H1 headlines
There are 5 <h1> headlines (“Garanta 20% de desconto nas turmas de 2026 e 2027”, “Garanta até 20% OFF + Bônus Exclusivos antecipand…” and “Aprender francês pode ser a aventura mais diverti…”). One clear main headline is easier for people and search engines.
80 internal links, 14 external
The homepage links to 80 pages on aliancafrancesa.com.br and 14 external pages.
7 checks passed
Meta description: 153 characters
Your meta description is 153 characters: “90 anos promovendo a língua francesa em São Paulo. Temos cursos de francês do nível iniciante até especialização para v…”.
Title: 50 characters
Your title is a healthy 50 characters: “Cursos de Francês e Cultura com a Aliança Francesa”.
Canonical URL set
The canonical URL is https://www.aliancafrancesa.com.br/.
Structured data in place
Structured data found: CollectionPage, Person 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://www.aliancafrancesa.com.br/sitemap_index.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.
No llms.txt
There is no https://www.aliancafrancesa.com.br/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 (2,751 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://www.aliancafrancesa.com.br/cursos/cursos-preparatorios is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://www.aliancafrancesa.com.br/cursos/cursos-preparatorios has no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.aliancafrancesa.com.br/cursos/atelies, whose canonical is https://www.aliancafrancesa.com.br/categoria-produto/atelies. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
5 pages slow to respond
https://www.aliancafrancesa.com.br/trabalhe-conosco, https://www.aliancafrancesa.com.br/contato-e-suporte, https://www.aliancafrancesa.com.br/cursos/atelies, https://www.aliancafrancesa.com.br/cursos/cursos-preparatorios and https://www.aliancafrancesa.com.br/teste-de-nivel took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 37 found) and read each the way a search engine does.
4 checks passed
Linked pages load
5 pages of 15 loaded without an error (the rest turned automated requests away).
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 5 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://aliancafrancesa.apikidev.com/wp-content/uploads/2023/10/logo-af-white.png.
22 small tap targets
22 of 45 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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
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 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.
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 1,967 words of copy
The homepage carries about 1,967 words of visible text.
3 checks passed
4 short forms
4 short forms (7 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 3 testimonial or review blocks and 6 customer or partner logos.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 1 more (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
28 cookies set on arrival
28Opening the homepage sets 28 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.
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.
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 aliancafrancesa.com.br, 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
- E-commerce
- WooCommerce
- Analytics
- Google Tag Manager
- Hosting
- Servicos de Computacao e Provimento de Inf
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on aliancafrancesa.com.br, including 24 speed issues, 1 SEO issue 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.