Website review, no card needed

fouani.com logo

fouani.com website review

Visit site (opens in a new tab)Reviewed 30 October 202650 issues · 88 checks

This review found 50 issues worth fixing on fouani.com, 20 of them high impact, across 88 checks. The most urgent: use efficient cache lifetimes. 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
3.6 s2.8 sMay 9Oct 243.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.3 s
May 16, 20263.4 s
May 23, 20263.4 s
May 30, 20263.3 s
Jun 6, 20263.1 s
Jun 13, 20262.9 s
Jun 20, 20262.9 s
Jun 27, 20263.2 s
Jul 4, 20263.2 s
Jul 11, 20263.3 s
Jul 18, 20263.3 s
Jul 25, 20263.3 s
Aug 1, 20263.4 s
Aug 8, 20263.5 s
Aug 15, 20263.3 s
Aug 22, 20263.3 s
Aug 29, 20263.3 s
Sep 5, 20263.1 s
Sep 12, 20263.2 s
Sep 19, 20263.0 s
Sep 26, 20263.0 s
Oct 3, 20263.0 s
Oct 10, 20263.1 s
Oct 17, 20263.3 s
Oct 24, 20263.2 s
Real-visitor tap response (INP)75th percentile, phones
166 ms132 msMay 9Oct 24158 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026153 ms
May 16, 2026153 ms
May 23, 2026154 ms
May 30, 2026147 ms
Jun 6, 2026149 ms
Jun 13, 2026154 ms
Jun 20, 2026153 ms
Jun 27, 2026162 ms
Jul 4, 2026155 ms
Jul 11, 2026150 ms
Jul 18, 2026152 ms
Jul 25, 2026152 ms
Aug 1, 2026145 ms
Aug 8, 2026147 ms
Aug 15, 2026138 ms
Aug 22, 2026136 ms
Aug 29, 2026156 ms
Sep 5, 2026147 ms
Sep 12, 2026156 ms
Sep 19, 2026144 ms
Sep 26, 2026137 ms
Oct 3, 2026137 ms
Oct 10, 2026146 ms
Oct 17, 2026158 ms
Oct 24, 2026158 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 fouani.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. fouani.com at 0.4 s0.4 s
  2. fouani.com at 0.8 s0.8 s
  3. fouani.com at 1.1 s1.1 s
  4. fouani.com at 1.5 s1.5 s
  5. fouani.com at 1.9 s1.9 s
  6. fouani.com at 2.3 s2.3 s
  7. fouani.com at 2.6 s2.6 s
  8. fouani.com at 3.0 s3.0 s

Speed

10 to fix29
  • Use efficient cache lifetimes

    1.2 s · 5.7 MB

    38 files are served with short cache lifetimes, so returning visitors download them again (5.7 MB).

  • Reduce unused JavaScript

    2.0 s · 1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.0 s faster on a phone.

  • Mobile performance score: 29

    29/100

    Your mobile performance score is 29. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Improve image delivery

    4.0 MB

    9 images could be 4.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Yandex APIs and Yandex CDN and others), adding 1.9 MB and 1.1 s of main-thread time.

  • Render-blocking requests

    750 ms

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.

  • Google CDN adds 469 ms

    469 ms

    Google CDN costs a phone 469 ms of main-thread work and 734 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.

  • Minify JavaScript

    300 ms · 53 KiB

    53 KiB could be saved by minifying JavaScript.

  • Main-thread work: 2.5 s

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

  • Yandex CDN adds 176 ms

    176 ms

    Yandex CDN costs a phone 176 ms of main-thread work and 697 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 · 248 KiB

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

  • 9 long tasks on the main thread

    9 long tasks block the main thread while loading, the longest for 224 ms. During a long task the page ignores taps.

  • Document request latency

    32 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Minify CSS

    22 KiB

    22 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: 105 ms

    105 ms

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

Core Web Vitals

11 to fix67
  • 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.

  • Time to Interactive: 29.7 s

    29.7 s

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

  • Largest Contentful Paint: 8.2 s

    8.2 s

    Your largest element takes 8.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Cumulative Layout Shift: 0.881

    0.881

    The layout shifts by 0.881 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Speed Index: 9.8 s

    9.8 s

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

  • Real-user LCP: 3.2 s

    3.2 s

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

  • Real-user FCP: 2.3 s

    2.3 s

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

  • Real-user TTFB: 1.5 s

    1.5 s

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

  • Total Blocking Time: 464 ms

    464 ms

    Scripts block taps and scrolling for 464 ms in total while the page loads. Good is under 200 ms.

  • First Contentful Paint: 1.9 s

    1.9 s

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

  • 2 images without width and height

    2 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +3%

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

  • Largest content (LCP) held steady for real visitors

    -2%

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

2 checks passed
  • Real-user INP: 156 ms

    156 ms

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

  • Real-user CLS: 0.05

    0.05

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

Images and page weight

5 to fix18
  • Page weight: 7.9 MB in 59 requests

    7.9 MB

    Your homepage downloads 7.9 MB in 59 requests on a phone: images 5.1 MB (27), scripts 1.9 MB (15) and other files 348 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

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

  • 1 image far larger than shown

    1.7 MB

    1 image is downloaded at several times the size a phone draws it, for example 1.png at 1,920 px wide, shown at 350 px. Resized copies would save about 1.7 MB.

  • 12 images in older formats

    12 images (3.8 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.

  • 9 images below the first screen load straight away

    9 images further down the page (376 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.3 g of CO₂ per visit

    2.25 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.25 g of CO₂e: 270.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 7386
  • Unlabelled dropdowns

    1 dropdown has no label.

  • 12 text elements with low contrast

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

  • Orphan list items

    Some list items are not inside a list.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 10 images without alt text

    10 images have no alt text, which hurts accessibility and image search.

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

    All page content should be contained by landmarks: 11 elements on the page fail this check, rated moderate by axe-core.

  • 5 links without text

    5 visible links have no text or label, so screen readers cannot say where they go.

  • 2 form fields without a label

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

1 checks passed
  • 37 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: 37 passed and 7 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

7 to fixGoogle 8360
  • No meta description

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

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (4 characters)

    Your title is only 4 characters: “Home”. 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.

  • 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 favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 19 internal links, 5 external

    The homepage links to 19 pages on fouani.com and 5 external pages.

2 checks passed
  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://fouani.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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://fouani.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.

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 (965 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix58
  • 3 linked pages are broken

    Your homepage links to https://fouani.com/1/terms-conditions, https://fouani.com/2/privacy-policy and https://fouani.com/3/cookie-policy, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 6 pages share 2 titles

    /, https://fouani.com/ng, https://fouani.com/lr and https://fouani.com/cg all use the title “Home”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 7 pages without a meta description

    https://fouani.com/contactus, https://fouani.com/careers, https://fouani.com/ng, https://fouani.com/lr, https://fouani.com/cg and https://fouani.com/gn and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages without an H1

    https://fouani.com/contactus, https://fouani.com/careers, https://fouani.com/lr, https://fouani.com/gn and https://fouani.com/gm have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://fouani.com/gn and https://fouani.com/gm 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.

  • 10 internal pages checked

    We fetched 10 pages linked from your homepage 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.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 7 pages that loaded have a <title>.

Best practices

2 to fixGoogle 8891
  • 11 small tap targets

    11 of 11 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 4 distorted images

    4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 5 low-resolution images

    5 images are served at too low a resolution for sharp phone screens.

2 checks passed
  • No console errors

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix86
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • About 672 words of copy

    The homepage carries about 672 words of visible text.

6 checks passed
  • Clear next step on the first screen

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

  • 2 calls to action

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

  • 2 short forms

    2 short forms (5 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Yandex Metrica (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 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.

  • 9 other companies contacted

    Loading the homepage contacts 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

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 fouani.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Analytics
Google Analytics
Hosting
Inmotion

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 50 issues on fouani.com, including 21 speed issues, 7 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

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