Website review, no card needed
wiiafrik.com website review
Visit site (opens in a new tab)Reviewed 10 November 202630 issues · 76 checks
This review found 30 issues worth fixing on wiiafrik.com, 11 of them high impact, across 76 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
78CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Use efficient cache lifetimes
9.3 s · 2.4 MB36 files are served with short cache lifetimes, so returning visitors download them again (2.4 MB).
Improve image delivery
2.9 s · 577 KiB2 images could be 577 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.9 s faster on a phone.
Render-blocking requests
3.0 s11 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.0 s.
Reduce unused CSS
920 ms · 182 KiBAbout 182 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 920 ms faster on a phone.
Mobile performance score: 62
62/100Your mobile performance score is 62. Pages that score under 90 lose visitors before the first paint.
Font display
650 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 650 ms).
Reduce unused JavaScript
460 ms · 84 KiBAbout 84 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 460 ms faster on a phone.
Minify JavaScript
150 ms · 34 KiB34 KiB could be saved by minifying JavaScript.
Minify CSS
150 ms · 31 KiB31 KiB could be saved by minifying CSS.
1 third-party service on the page
1 third-party service load with your homepage (Google Fonts), adding 87 KiB and 0 ms of main-thread time.
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.
2 checks passed
Main-thread work: 1.0 s
A phone's processor spends 1.0 s on main-thread work while loading, 180 ms of it running JavaScript. That is comfortably low.
Server response: 28 ms
28 msYour server sent the HTML in 28 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 45.7 s
45.7 sYour largest element takes 45.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Technologie Wiiafrik”.
Time to Interactive: 48.6 s
48.6 sThe page becomes fully interactive after 48.6 s. Good is under 3.8 s.
Speed Index: 9.2 s
9.2 sVisually, the page fills in at 9.2 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
3 images without width and height
3 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.
2 checks passed
Cumulative Layout Shift: 0.06
0.06The layout barely moves while loading (CLS 0.06, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 18.1 MB in 53 requests
18.1 MBYour homepage downloads 18.1 MB in 53 requests on a phone: images 12.7 MB (12), media 3.7 MB (2) and fonts 1.3 MB (9). Under 2 MB keeps phones on slow connections fast.
6 images over 500 KB
6 images weigh 11.6 MB together. On a phone connection a single image that size takes seconds.
6 images far larger than shown
6.1 MB6 images are downloaded at several times the size a phone draws them, for example sj5rt4IYqTX4I1uEjmnFHoKj1OPCvc98C8ZuP2I7.png at 1,536 px wide, shown at 358 px. Resized copies would save about 6.1 MB.
7 images in older formats
7 images (11.7 MB) 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.
6 images below the first screen load straight away
6 images further down the page (11.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 5.1 g of CO₂ per visit
5.13 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.13 g of CO₂e: 615.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
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.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 10 images in the HTML carry an alt attribute.
31 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 35 WCAG 2.2 A/AA and best-practice rules on the phone render: 31 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
Title is long (73 characters)
Your title is 73 characters, so Google will cut it off around 60: “Wiiafrik | Securite, electricite, froid, forage, informatique et telecoms”.
Meta description is long (206 characters)
Your meta description is 206 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (LocalBusiness) but with 1 problem, for example “LocalBusiness: sameAs is an empty list”.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
38 internal links, 0 external
The homepage links to 38 pages on wiiafrik.com and 0 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Wiiafrik, entreprise de technologie DEMANDER UN DEVIS”.
Canonical URL set
The canonical URL is https://wiiafrik.com/.
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.
XML sitemap found
Your XML sitemap is reachable at https://wiiafrik.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://wiiafrik.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.
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, description and contact details; logo and sameAs (social profiles) would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (416 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages without an H1
https://wiiafrik.com/contact and https://wiiafrik.com/projets have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://wiiafrik.com/projets, https://wiiafrik.com/boutique and https://wiiafrik.com/demande-devis have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
5 internal pages checked
We fetched 5 pages linked from your homepage and read each the way a search engine does.
6 checks passed
Linked pages load
All 5 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 a meta description
All 5 pages that loaded have a meta description.
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.
Every page has a title
All 5 pages that loaded have a <title>.
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: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
13 of 14 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
Only about 159 words
The homepage has only about 159 words of visible text; thin pages give Google and first-time buyers little to go on.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact”.
3 calls to action
The homepage has 3 calls to action, for example “Contact” and “CONTACT”.
Direct contact links
Visitors can reach you directly: 4 phone links and 5 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
2 cookies set on arrival
2Opening the homepage sets 2 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.
2 other companies contacted
Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 wiiafrik.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Hosting
- O2switch O2switch Sas
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on wiiafrik.com, including 12 speed issues, 4 SEO issues 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.