Website review, no card needed

sotufab.tn logo

sotufab.tn website review

Visit site (opens in a new tab)Reviewed 24 October 202633 issues · 75 checks

This review found 33 issues worth fixing on sotufab.tn, 13 of them high impact, across 75 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.7 s899 msMay 2Oct 171.1 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.8 s
May 9, 20261.7 s
May 16, 20261.7 s
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.8 s
Jun 13, 20261.9 s
Jun 20, 20261.9 s
Jun 27, 20262.2 s
Jul 4, 20262.1 s
Jul 11, 20261.9 s
Jul 18, 20261.9 s
Jul 25, 20261.7 s
Aug 1, 20261.5 s
Aug 8, 20261.3 s
Aug 15, 20261.2 s
Aug 22, 20261.3 s
Aug 29, 20261.9 s
Sep 5, 20262.3 s
Sep 12, 20262.5 s
Sep 19, 20262.4 s
Sep 26, 20262.1 s
Oct 3, 20261.3 s
Oct 10, 20261.1 s
Oct 17, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
151 ms106 msMay 2Oct 17146 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026116 ms
May 9, 2026114 ms
May 16, 2026113 ms
May 23, 2026112 ms
May 30, 2026111 ms
Jun 6, 2026112 ms
Jun 13, 2026114 ms
Jun 20, 2026118 ms
Jun 27, 2026121 ms
Jul 4, 2026122 ms
Jul 11, 2026124 ms
Jul 18, 2026124 ms
Jul 25, 2026124 ms
Aug 1, 2026122 ms
Aug 8, 2026121 ms
Aug 15, 2026119 ms
Aug 22, 2026118 ms
Aug 29, 2026120 ms
Sep 5, 2026123 ms
Sep 12, 2026128 ms
Sep 19, 2026128 ms
Sep 26, 2026128 ms
Oct 3, 2026128 ms
Oct 10, 2026136 ms
Oct 17, 2026146 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

Full-page screenshot of sotufab.tn (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sotufab.tn at 0.8 s0.8 s
  2. sotufab.tn at 1.5 s1.5 s
  3. sotufab.tn at 2.3 s2.3 s
  4. sotufab.tn at 3.1 s3.1 s
  5. sotufab.tn at 3.9 s3.9 s
  6. sotufab.tn at 4.6 s4.6 s
  7. sotufab.tn at 5.4 s5.4 s
  8. sotufab.tn at 6.2 s6.2 s

Speed

6 to fix68
  • Improve image delivery

    9.4 s · 1.9 MB

    3 images could be 1.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 9.4 s faster on a phone.

  • Render-blocking requests

    2.5 s

    23 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.5 s.

  • Mobile performance score: 68

    68/100

    Your mobile performance score is 68 (desktop: 85). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    600 ms · 102 KiB

    About 102 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.

  • 2,216 HTML elements

    The page has 2,216 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Main-thread work: 2.2 s

    A phone's processor spends 2.2 s on main-thread work while loading, 538 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 62 ms. During a long task the page ignores taps.

  • 1 third-party service on the page

    1 third-party service load with your homepage (Google Fonts), adding 98 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify CSS

    5 KiB

    5 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 318 ms

    318 ms

    Your server sent the HTML in 318 ms, well inside Google's 600 ms guideline.

Core Web Vitals

10 to fix33
  • 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: 2.0 s

    2.0 s

    Real visitors wait 2.0 s for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest Contentful Paint: 15.2 s

    15.2 s

    Your largest element takes 15.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Bureau junior SOTUFAB pour la rentrée 2026”.

  • Time to Interactive: 15.2 s

    15.2 s

    The page becomes fully interactive after 15.2 s. Good is under 3.8 s.

  • Real-user LCP: 2.8 s

    2.8 s

    Real visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 215 ms

    215 ms

    Real visitors wait 215 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Tap response (INP) got 23% slower for real visitors

    +23%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 116 ms to 146 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Real-user FCP: 2.5 s

    2.5 s

    Real visitors see the first content after 2.5 s (75th percentile). Good is under 1.8 s.

  • Speed Index: 5.2 s

    5.2 s

    Visually, the page fills in at 5.2 s (Speed Index). Good is under 3.4 s.

  • First Contentful Paint: 2.4 s

    2.4 s

    The first text or image appears after 2.4 s on a phone. Good is under 1.8 s.

4 checks passed
  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Largest content (LCP) got 36% faster for real visitors

    -36%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0.008

    0.008

    The layout barely moves while loading (CLS 0.008, good is under 0.1).

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

4 to fix25
  • Page weight: 4.1 MB in 60 requests

    4.1 MB

    Your homepage downloads 4.1 MB in 60 requests on a phone: images 3.6 MB (11), fonts 239 KiB (10) and stylesheets 189 KiB (32). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 2.4 MB together. On a phone connection a single image that size takes seconds.

  • 5 images far larger than shown

    2.2 MB

    5 images are downloaded at several times the size a phone draws them, for example ChatGPT-Image-Aug-27-2026-01_14_44-PM.png at 1,672 px wide, shown at 370 px. Resized copies would save about 2.2 MB.

  • 7 images in older formats

    7 images (3.4 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 (74 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.2 g of CO₂ per visit

    1.17 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.17 g of CO₂e: 140.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

8 to fixGoogle 8790
  • 9 tap targets too small

    9 tap targets are too small or too close together to hit reliably with a finger.

  • 6 text elements with low contrast

    6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (6 elements)

    All page content should be contained by landmarks: 6 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.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

    Headings skip levels (h2 → h6 and h3 → h6), which makes the page harder to scan with a screen reader.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (8 elements).

2 checks passed
  • Every image has alt text

    All 45 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 8581
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is long (78 characters)

    Your title is 78 characters, so Google will cut it off around 60: “Sotufab Meubles - Designer et fabricant de meuble en Tunisie - SOTUFAB Meubles”.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 254 internal links, 5 external

    The homepage links to 254 pages on sotufab.tn and 5 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Du style pour chaque pièce”.

  • Canonical URL set

    The canonical URL is https://sotufab.tn/.

  • Structured data in place

    Structured data found: BreadcrumbList, FAQPage, ImageObject, Organization and WebPage.

  • 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://sotufab.tn/sitemap.xml.

AI search readiness

100
4 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, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,412 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://sotufab.tn/llms.txt (4 KiB, 28 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 98 found) and read each the way a search engine does.

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

Google 96100
  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    34 of 42 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

    Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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,403 words of copy

    The homepage carries about 1,403 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact”.

  • 3 short forms

    3 short forms (3 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics and Meta Pixel.

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.

  • 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 sotufab.tn, 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 Analytics

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on sotufab.tn, including 16 speed issues, 3 SEO issues and 2 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25