Website review, no card needed
affilizz.com website review
Visit site (opens in a new tab)Reviewed 17 November 202626 issues · 58 checks
This review found 26 issues worth fixing on affilizz.com, 10 of them high impact, across 58 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
80BClosest competitors among reviewed websites
Compare side by sideOne 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
Use efficient cache lifetimes
2.6 s · 11.1 MB10 files are served with short cache lifetimes, so returning visitors download them again (11.1 MB).
Reduce unused JavaScript
5.3 s · 831 KiBAbout 831 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.3 s faster on a phone.
Avoid multiple page redirects
4.2 sThe page goes through 1 redirect before it starts loading, costing about 4.2 s. Link and advertise the final URL directly.
Render-blocking requests
1.6 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
8 third-party services on the page
8 third-party services load with your homepage (website-files.com, Hubspot and weglot.com and others), adding 11.9 MB and 766 ms of main-thread time.
website-files.com adds 293 ms
293 mswebsite-files.com costs a phone 293 ms of main-thread work and 11.1 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.
Mobile performance score: 62
62/100Your mobile performance score is 62. Pages that score under 90 lose visitors before the first paint.
Main-thread work: 3.0 s
A phone's processor spends 3.0 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Hubspot adds 248 ms
248 msHubspot costs a phone 248 ms of main-thread work and 408 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.
Reduce unused CSS
150 ms · 43 KiBAbout 43 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.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 82 ms. During a long task the page ignores taps.
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: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 15.4 s
15.4 sYour largest element takes 15.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 15.6 s
15.6 sThe page becomes fully interactive after 15.6 s. Good is under 3.8 s.
First Contentful Paint: 4.5 s
4.5 sThe first text or image appears after 4.5 s on a phone. Good is under 1.8 s.
59 images without width and height
59 images have no width and height attributes, so the layout jumps as each one loads.
Speed Index: 5.0 s
5.0 sVisually, the page fills in at 5.0 s (Speed Index). Good is under 3.4 s.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
Total Blocking Time: 126 ms
126 msScripts block the page for only 126 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 23.8 MB in 153 requests
23.8 MBYour homepage downloads 23.8 MB in 153 requests on a phone: media 21.2 MB (8), scripts 1.3 MB (32) and images 661 KiB (76). Under 2 MB keeps phones on slow connections fast.
About 6.7 g of CO₂ per visit
6.75 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.75 g of CO₂e: 809.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
Form elements do not have associated labels
Form elements do not have associated labels (1 element).
3 links without text
3 links have no text or label, so screen readers cannot say where they go.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Headings skip levels
Headings skip levels (h1 → h4, h2 → h4 and h3 → h6), which makes the page harder to scan with a screen reader.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
48 internal links, 10 external
The homepage links to 48 pages on affilizz.com and 10 external pages.
6 checks passed
Meta description: 80 characters
Your meta description is 80 characters: “Votre meta plateforme d'affiliation, de la création de contenu à la facturation.”.
One H1 headline
Your main headline reads: “Libérer le potentiel de l'affiliation pour les créateurs de contenu”.
Title: 49 characters
Your title is a healthy 49 characters: “L'outil unique pour gérer toute votre affiliation”.
Canonical URL set
The canonical URL is https://www.affilizz.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.affilizz.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.
No llms.txt
There is no https://www.affilizz.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.
1 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.
Other pages
6 pages share a title
https://www.affilizz.com/case-study/nouillespc-automatiser-laffiliation-pour-mieux-accompagner-sa-communaute-discord, https://www.affilizz.com/case-study/aide-redaction-bons-plans, https://www.affilizz.com/case-study/french-hardware-live-shopping-youtube-et-discord, https://www.affilizz.com/case-study/le-point-services-3-millions-de-chiffres-daffaires-2024-chez-ses-marchands-partenaires, https://www.affilizz.com/case-study/patissier-a-editeur-de-sites-un-complement-de-revenus-avec-laffiliation and https://www.affilizz.com/case-study/qwant-boost-son-offre-publicitaire-grace-a-laffiliation all use the title “Affilizz”. Search engines can't tell which page to show for a search, so each competes with the others.
6 pages without a meta description
https://www.affilizz.com/case-study/nouillespc-automatiser-laffiliation-pour-mieux-accompagner-sa-communaute-discord, https://www.affilizz.com/case-study/aide-redaction-bons-plans, https://www.affilizz.com/case-study/french-hardware-live-shopping-youtube-et-discord, https://www.affilizz.com/case-study/le-point-services-3-millions-de-chiffres-daffaires-2024-chez-ses-marchands-partenaires, https://www.affilizz.com/case-study/patissier-a-editeur-de-sites-un-complement-de-revenus-avec-laffiliation and https://www.affilizz.com/case-study/qwant-boost-son-offre-publicitaire-grace-a-laffiliation 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 19 found) and read each the way a search engine does.
5 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.
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
4 console errors
4 errors were logged to the browser console during Google's test (“Failed to load resource: the server responded with a status of 403 (Forbidden)”).
1 checks passed
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 2,211 words of copy
The homepage carries about 2,211 words of visible text.
4 checks passed
2 calls to action
The homepage has 2 calls to action, for example “E-book”.
2 short forms
2 short forms (4 fields at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 89 testimonial or review blocks, 1 customer or partner logo and 1 trust badge.
Analytics in place
Analytics detected: HubSpot.
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 affilizz.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2025.
Stack
- CMS
- Webflow
- Framework
- jQuery
- Hosting
- Webflow
Hiring
- Hiring
- 1 open role
- Job board
- careers page
- Careers page
- www.affilizz.com/jobs (opens in a new tab)
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 26 issues on affilizz.com, including 14 speed issues, 3 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.