Website review, no card needed

afniah.com logo

afniah.com website review

Visit site (opens in a new tab)Reviewed 18 October 202638 issues · 75 checks

This review found 38 issues worth fixing on afniah.com, 12 of them high impact, across 75 checks. The most urgent: render-blocking requests. 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.2 s1.9 sJun 27Sep 53.0 s
Show as table
DateReal-visitor load time (LCP)
Jun 27, 20262.1 s
Jul 4, 20262.0 s
Jul 11, 20262.1 s
Jul 18, 20262.1 s
Jul 25, 20262.1 s
Aug 8, 20262.1 s
Aug 15, 20262.1 s
Aug 22, 20262.4 s
Aug 29, 20262.6 s
Sep 5, 20263.0 s

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 afniah.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. afniah.com at 1.3 s1.3 s
  2. afniah.com at 2.6 s2.6 s
  3. afniah.com at 3.9 s3.9 s
  4. afniah.com at 5.2 s5.2 s
  5. afniah.com at 6.5 s6.5 s
  6. afniah.com at 7.8 s7.8 s
  7. afniah.com at 9.1 s9.1 s
  8. afniah.com at 10.4 s10.4 s

Speed

6 to fix69
  • Render-blocking requests

    1.5 s

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

  • Use efficient cache lifetimes

    2.0 MB

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

  • Mobile performance score: 69

    69/100

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

  • Reduce unused JavaScript

    650 ms · 292 KiB

    About 292 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 650 ms faster on a phone.

  • Google Tag Manager adds 343 ms

    343 ms

    Google Tag Manager costs a phone 343 ms of main-thread work and 527 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.

  • Improve image delivery

    286 KiB

    4 images could be 286 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google Tag Manager, Google Analytics and Google Fonts), adding 600 KiB and 343 ms of main-thread time.

  • Reduce unused CSS

    150 ms · 30 KiB

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

  • 5 long tasks on the main thread

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

  • Minify CSS

    9 KiB

    9 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: 0.7 s

    A phone's processor spends 0.7 s on main-thread work while loading, 299 ms of it running JavaScript. That is comfortably low.

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

6 to fix79
  • Speed Index: 9.1 s

    9.1 s

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

  • First Contentful Paint: 3.6 s

    3.6 s

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

  • Largest Contentful Paint: 4.4 s

    4.4 s

    Your largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “In Afniah, we seek to create critical dialogue at the natio…”. Most of its time is element render delay (4.1 s).

  • Time to Interactive: 7.7 s

    7.7 s

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

  • Largest content (LCP) got 37% slower for real visitors

    +37%

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

  • 9 images without width and height

    9 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
  • Total Blocking Time: 109 ms

    109 ms

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

  • Cumulative Layout Shift: 0.021

    0.021

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

Images and page weight

1 to fix85
  • Page weight: 2.7 MB in 35 requests

    2.7 MB

    Your homepage downloads 2.7 MB in 35 requests on a phone: images 2.0 MB (19), scripts 613 KiB (5) and fonts 64 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • About 0.8 g of CO₂ per visit

    0.76 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

11 to fixGoogle 4577
  • Orphan list items

    Some list items are not inside a list.

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • Malformed lists

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

  • 16 images without alt text

    16 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.

  • 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.

  • 8 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

1 checks passed
  • 22 automated accessibility rules passed

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

SEO

7 to fixGoogle 8257
  • 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 (18 characters)

    Your title is only 18 characters: “Home Page - AFNIAH”. 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 XML sitemap

    No XML sitemap at https://www.afniah.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at afniah.com/robots.txt, the first file search crawlers ask for.

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • 60 internal links, 4 external

    The homepage links to 60 pages on afniah.com and 4 external pages.

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://www.afniah.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

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

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

Other pages

2 to fix90
  • 15 pages without a meta description

    https://www.afniah.com/en/Expertise/ExpertiseListing/bfbc61bf-4e26-4405-960b-170c0cf75f2f, https://www.afniah.com/en/Expertise/ExpertiseListing/dd38cc07-361f-49cf-8088-e089b3c0c218, https://www.afniah.com/en/Expertise/ExpertiseListing/37590769-bac4-4c31-a926-380f4727265f, https://www.afniah.com/en/Expertise/ExpertiseListing/0c9d9dc3-9018-43af-9c14-4f45accb0997, https://www.afniah.com/en/Expertise/ExpertiseListing/13ff69e9-976d-41da-a330-044224ba6018 and https://www.afniah.com/en/Expertise/ExpertiseListing/2c5f65f6-7f01-45f8-b652-1ace60e58d5e and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://www.afniah.com/en/Expertise/ExpertiseListing/bfbc61bf-4e26-4405-960b-170c0cf75f2f, https://www.afniah.com/en/Expertise/ExpertiseListing/dd38cc07-361f-49cf-8088-e089b3c0c218, https://www.afniah.com/en/Expertise/ExpertiseListing/37590769-bac4-4c31-a926-380f4727265f, https://www.afniah.com/en/Expertise/ExpertiseListing/0c9d9dc3-9018-43af-9c14-4f45accb0997, https://www.afniah.com/en/Expertise/ExpertiseListing/13ff69e9-976d-41da-a330-044224ba6018 and https://www.afniah.com/en/Expertise/ExpertiseListing/2c5f65f6-7f01-45f8-b652-1ace60e58d5e and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 29 small tap targets

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

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

2 to fix75
  • No social proof

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

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

    The homepage carries about 469 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 US”.

  • 2 calls to action

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

  • 1 short form

    A short form (0 fields at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.

  • 6 other companies contacted

    Loading the homepage contacts 6 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 afniah.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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on afniah.com, including 12 speed issues, 7 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