Website review, no card needed
wekolo.com website review
Visit site (opens in a new tab)Reviewed 9 November 202629 issues · 63 checks
This review found 29 issues worth fixing on wekolo.com, 12 of them high impact, across 63 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
71CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Use efficient cache lifetimes
7.5 s · 2.3 MB113 files are served with short cache lifetimes, so returning visitors download them again (2.3 MB).
Render-blocking requests
4.6 s38 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.6 s.
Reduce unused JavaScript
1.6 s · 743 KiBAbout 743 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.
Reduce unused CSS
1.5 s · 287 KiBAbout 287 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Mobile performance score: 51
51/100Your mobile performance score is 51. 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, Hubspot and usemessages.com and others), adding 950 KiB and 627 ms of main-thread time.
Google Tag Manager adds 506 ms
506 msGoogle Tag Manager costs a phone 506 ms of main-thread work and 759 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
300 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 300 ms).
Main-thread work: 2.8 s
A phone's processor spends 2.8 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 143 ms. During a long task the page ignores taps.
Legacy JavaScript
14 KiBPolyfills for old browsers add 14 KiB JavaScript that modern phones do not need.
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
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: 74 ms
74 msYour server sent the HTML in 74 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 10.4 s
10.4 sYour largest element takes 10.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 19.0 s
19.0 sThe page becomes fully interactive after 19.0 s. Good is under 3.8 s.
Speed Index: 11.7 s
11.7 sVisually, the page fills in at 11.7 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.8 s
3.8 sThe first text or image appears after 3.8 s on a phone. Good is under 1.8 s.
Total Blocking Time: 330 ms
330 msScripts block taps and scrolling for 330 ms in total while the page loads. Good is under 200 ms.
13 images without width and height
13 images have no width and height attributes, so the layout jumps as each one loads.
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.
1 checks passed
Cumulative Layout Shift: 0.003
0.003The layout barely moves while loading (CLS 0.003, good is under 0.1).
Images and page weight
Page weight: 3.2 MB in 136 requests
3.2 MBYour homepage downloads 3.2 MB in 136 requests on a phone: scripts 1.8 MB (42), images 624 KiB (40) and stylesheets 472 KiB (36). Under 2 MB keeps phones on slow connections fast.
About 0.9 g of CO₂ per visit
0.90 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.90 g of CO₂e: 107.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 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.
2 checks passed
Every image has alt text
All 57 images in the HTML carry an alt attribute.
11 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 13 WCAG 2.2 A/AA and best-practice rules on the phone render: 11 passed and 2 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
41 internal links, 5 external
The homepage links to 41 pages on wekolo.com and 5 external pages.
7 checks passed
Meta description: 151 characters
Your meta description is 151 characters: “Wekolo est une solution SAAS qui permet aux enseignes (franchises et groupements) de gérer et d'optimiser le marketing …”.
Title: 57 characters
Your title is a healthy 57 characters: “Wekolo - Marketing digital des réseaux de points de vente”.
Canonical URL set
The canonical URL is https://www.wekolo.com/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage 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.wekolo.com/sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://www.wekolo.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
9 linked pages are broken
Your homepage links to https://www.wekolo.com/fonctionnalite-galerie, https://www.wekolo.com/demander-une-demo, https://www.wekolo.com/agence-marketing, https://www.wekolo.com/contact-wekolo, https://www.wekolo.com/fonctionnalites and https://www.wekolo.com/module-ticketing and 3 others, which answer with an error. Visitors hit a dead end and search engines drop them.
1 page without a title
https://www.wekolo.com/module-rapport has no <title>, so Google invents the link text in results.
2 pages without a meta description
https://www.wekolo.com/centre-daide and https://www.wekolo.com/module-rapport have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages share a meta description
https://www.wekolo.com/fonctionnalite-ticketing, https://www.wekolo.com/fonctionnalite-moderation, https://www.wekolo.com/fonctionnalite-planning and https://www.wekolo.com/fonctionnalite-rapport use the same meta description. A description written for each page earns more clicks.
2 pages without an H1
https://www.wekolo.com/centre-daide and https://www.wekolo.com/module-rapport have no <h1> headline, so visitors and search engines get no clear main topic.
5 pages slow to respond
https://www.wekolo.com/fonctionnalite-ticketing, https://www.wekolo.com/fonctionnalite-moderation, https://www.wekolo.com/fonctionnalite-planning, https://www.wekolo.com/fonctionnalite-rapport and https://www.wekolo.com/module-rapport took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 17 found) and read each the way a search engine does.
3 checks passed
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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 500 ()”.
1 checks passed
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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
Only about 13 words
The homepage has only about 13 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
3 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Contact”.
Social proof on the page
Social proof on the homepage: 42 testimonial or review blocks, a star rating and 3 trust badges.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and HubSpot.
Privacy and tracking
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.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 wekolo.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
- Google Analytics | Google Tag Manager
- Hosting
- IONOS
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 wekolo.com, including 15 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.