Website review, no card needed
kfc.com.tn website review
Visit site (opens in a new tab)Reviewed 23 October 202649 issues · 89 checks
This review found 49 issues worth fixing on kfc.com.tn, 27 of them high impact, across 89 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
58F- #115,547 of 117,602 reviewed websitesbeats 1%
- #66,574 of 66,923 online storesbeats 0%
- #159 of 166 PrestaShop storesbeats 3%
Closest competitors among PrestaShop stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 7.9 s |
| May 9, 2026 | 8.5 s |
| May 16, 2026 | 8.6 s |
| May 23, 2026 | 9.1 s |
| May 30, 2026 | 9.4 s |
| Jun 6, 2026 | 9.2 s |
| Jun 13, 2026 | 8.8 s |
| Jun 20, 2026 | 8.3 s |
| Jun 27, 2026 | 7.5 s |
| Jul 4, 2026 | 6.5 s |
| Jul 11, 2026 | 5.3 s |
| Jul 18, 2026 | 5.1 s |
| Jul 25, 2026 | 6.1 s |
| Aug 1, 2026 | 7.1 s |
| Aug 8, 2026 | 7.9 s |
| Aug 15, 2026 | 8.1 s |
| Aug 22, 2026 | 8.3 s |
| Aug 29, 2026 | 8.2 s |
| Sep 5, 2026 | 8.3 s |
| Sep 12, 2026 | 8.3 s |
| Sep 19, 2026 | 8.3 s |
| Sep 26, 2026 | 8.3 s |
| Oct 3, 2026 | 8.2 s |
| Oct 10, 2026 | 8.2 s |
| Oct 17, 2026 | 8.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 115 ms |
| May 9, 2026 | 125 ms |
| May 16, 2026 | 120 ms |
| May 23, 2026 | 116 ms |
| May 30, 2026 | 112 ms |
| Jun 6, 2026 | 114 ms |
| Jun 13, 2026 | 115 ms |
| Jun 20, 2026 | 121 ms |
| Jun 27, 2026 | 117 ms |
| Jul 4, 2026 | 114 ms |
| Jul 11, 2026 | 110 ms |
| Jul 18, 2026 | 111 ms |
| Jul 25, 2026 | 113 ms |
| Aug 1, 2026 | 113 ms |
| Aug 8, 2026 | 119 ms |
| Aug 15, 2026 | 117 ms |
| Aug 22, 2026 | 116 ms |
| Aug 29, 2026 | 110 ms |
| Sep 5, 2026 | 107 ms |
| Sep 12, 2026 | 107 ms |
| Sep 19, 2026 | 106 ms |
| Sep 26, 2026 | 110 ms |
| Oct 3, 2026 | 112 ms |
| Oct 10, 2026 | 116 ms |
| Oct 17, 2026 | 112 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
Speed
Use efficient cache lifetimes
30.4 s · 8.9 MB123 files are served with short cache lifetimes, so returning visitors download them again (8.9 MB).
Improve image delivery
25.4 s · 5.4 MB19 images could be 5.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 25.4 s faster on a phone.
Render-blocking requests
3.3 s30 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.3 s.
Font display
3.0 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 3.0 s).
Reduce unused JavaScript
1.8 s · 372 KiBAbout 372 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.
Mobile performance score: 33
33/100Your mobile performance score is 33 (desktop: 37). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Legacy JavaScript
300 ms · 22 KiBPolyfills for old browsers add 22 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
2,513 HTML elements
The page has 2,513 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused CSS
290 ms · 41 KiBAbout 41 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 290 ms faster on a phone.
7 third-party services on the page
7 third-party services load with your homepage (Mapbox, Cloudflare CDN and Google CDN and others), adding 442 KiB and 141 ms of main-thread time.
Minify JavaScript
150 ms · 19 KiB19 KiB could be saved by minifying JavaScript.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 128 ms. During a long task the page ignores taps.
Minify CSS
110 ms · 11 KiB11 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.
2 checks passed
Main-thread work: 1.4 s
A phone's processor spends 1.4 s on main-thread work while loading, 448 ms of it running JavaScript. That is comfortably low.
Server response: 274 ms
274 msYour server sent the HTML in 274 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 LCP: 10.8 s
10.8 sReal visitors wait 10.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 1.04
1.04For real visitors the layout shifts by 1.04 (75th percentile). Good is under 0.1.
Real-user FCP: 8.8 s
8.8 sReal visitors see the first content after 8.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 7.6 s
7.6 sReal visitors wait 7.6 s for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 1.519
1.519The layout shifts by 1.519 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest Contentful Paint: 44.9 s
44.9 sYour largest element takes 44.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 22.8 s
22.8 sVisually, the page fills in at 22.8 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 45.7 s
45.7 sThe page becomes fully interactive after 45.7 s. Good is under 3.8 s.
First Contentful Paint: 3.6 s
3.6 sThe first text or image appears after 3.6 s on a phone. Good is under 1.8 s.
23 images without width and height
23 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 115 ms to 112 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 7.9 s to 8.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user INP: 125 ms
125 msReal visitors wait 125 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Total Blocking Time: 104 ms
104 msScripts block the page for only 104 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 9.4 MB in 138 requests
9.4 MBYour homepage downloads 9.4 MB in 138 requests on a phone: images 7.9 MB (67), scripts 732 KiB (32) and fonts 589 KiB (8). Under 2 MB keeps phones on slow connections fast.
3 images over 500 KB
3 images weigh 4.7 MB together. On a phone connection a single image that size takes seconds.
5 images far larger than shown
3.3 MB5 images are downloaded at several times the size a phone draws them, for example a2b4f4e57cc95c962de2817b5edb123dd0ae443c_7dt.png at 1,920 px wide, shown at 390 px. Resized copies would save about 3.3 MB.
40 images in older formats
40 images (7.5 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.
1 image below the first screen load straight away
1 image further down the page (189 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 2.7 g of CO₂ per visit
2.65 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.65 g of CO₂e: 318.4 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”.
Orphan list items
Some list items are not inside a list.
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
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 (h1 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
38 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 6 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 short (11 characters)
Your title is only 11 characters: “KFC Tunisie”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is short (27 characters)
Your meta description is only 27 characters: “Fameuses recettes de poulet”. 70 to 160 characters is enough to sell the click.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://kfc.com.tn/sitemap.xml, so Google discovers your pages only by following links.
3 links crawlers can't follow
3 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
157 internal links, 6 external
The homepage links to 157 pages on kfc.com.tn and 6 external pages.
2 checks passed
One H1 headline
Your main headline reads: “Notre menu”.
robots.txt in place
robots.txt is in place.
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://kfc.com.tn/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 (1,082 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page is broken
Your homepage links to https://kfc.com.tn/31-deals, which answers with an error. Visitors hit a dead end and search engines drop it.
2 linked pages hidden from search
https://kfc.com.tn/content/6-notre-aventure and https://kfc.com.tn/content/1-faq are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
11 pages without a meta description
https://kfc.com.tn/15-notre-carte-, https://kfc.com.tn/content/6-notre-aventure, https://kfc.com.tn/Magasins, https://kfc.com.tn/29-for-one, https://kfc.com.tn/30-sharing and https://kfc.com.tn/24-buckets and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.
10 pages without an H1
https://kfc.com.tn/15-notre-carte-, https://kfc.com.tn/nous-contacter, https://kfc.com.tn/29-for-one, https://kfc.com.tn/30-sharing, https://kfc.com.tn/24-buckets and https://kfc.com.tn/6-sandwiches and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.
14 pages slow to respond
https://kfc.com.tn/15-notre-carte-, https://kfc.com.tn/content/6-notre-aventure, https://kfc.com.tn/Magasins, https://kfc.com.tn/nous-contacter, https://kfc.com.tn/sitemap and https://kfc.com.tn/content/1-faq and 8 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 77 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.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://kfc.com.tn/.
13 small tap targets
13 of 61 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 401 ()”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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 169 words
The homepage has only about 169 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 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.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “[email protected]”.
2 calls to action
The homepage has 2 calls to action, for example “[email protected]”.
44 short forms
44 short forms (0 fields at most) are right on the homepage.
Direct contact links
Visitors can reach you directly: 0 phone links and 2 email links.
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.
8 other companies contacted
Loading the homepage contacts 8 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 kfc.com.tn, 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
- E-commerce
- PrestaShop
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 49 issues on kfc.com.tn, including 19 speed issues, 7 SEO issues and 5 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.