Website review, no card needed

aynalfahad.com logo

aynalfahad.com website review

Visit site (opens in a new tab)Reviewed 7 November 202639 issues · 63 checks

This review found 39 issues worth fixing on aynalfahad.com, 15 of them high impact, across 63 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
5.0 s3.9 sMay 16Oct 314.6 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20264.4 s
May 23, 20264.7 s
May 30, 20264.9 s
Jun 6, 20264.8 s
Jun 13, 20264.8 s
Jun 20, 20264.8 s
Jun 27, 20264.8 s
Jul 4, 20264.8 s
Jul 11, 20264.7 s
Jul 18, 20264.8 s
Jul 25, 20264.7 s
Aug 1, 20264.7 s
Aug 8, 20264.7 s
Aug 15, 20264.6 s
Aug 22, 20264.6 s
Aug 29, 20264.7 s
Sep 5, 20264.7 s
Sep 12, 20264.7 s
Sep 19, 20264.6 s
Sep 26, 20264.2 s
Oct 3, 20264.0 s
Oct 10, 20264.0 s
Oct 17, 20264.2 s
Oct 24, 20264.6 s
Oct 31, 20264.6 s
Real-visitor tap response (INP)75th percentile, phones
586 ms242 msMay 16Oct 31300 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026448 ms
May 23, 2026483 ms
May 30, 2026517 ms
Jun 6, 2026510 ms
Jun 13, 2026527 ms
Jun 20, 2026510 ms
Jun 27, 2026504 ms
Jul 4, 2026517 ms
Jul 11, 2026489 ms
Jul 18, 2026537 ms
Jul 25, 2026546 ms
Aug 1, 2026545 ms
Aug 8, 2026527 ms
Aug 15, 2026444 ms
Aug 22, 2026377 ms
Aug 29, 2026328 ms
Sep 5, 2026305 ms
Sep 12, 2026297 ms
Sep 19, 2026290 ms
Sep 26, 2026282 ms
Oct 3, 2026287 ms
Oct 10, 2026294 ms
Oct 17, 2026297 ms
Oct 24, 2026301 ms
Oct 31, 2026300 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 aynalfahad.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

6 to fix82
  • Use efficient cache lifetimes

    1.1 s · 17.8 MB

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

  • Reduce unused JavaScript

    1.2 s · 241 KiB

    About 241 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.

  • Improve image delivery

    8.7 MB

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

  • Mobile performance score: 82

    82/100

    Your mobile performance score is 82. Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    300 ms

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

  • 1,602 HTML elements

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (JSDelivr CDN, Cloudflare and Google Fonts and others), adding 528 KiB and 19 ms of main-thread time.

  • 3 long tasks on the main thread

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

  • Legacy JavaScript

    10 KiB

    Polyfills for old browsers add 10 KiB JavaScript that modern phones do not need.

  • 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
  • Main-thread work: 1.0 s

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

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 LCP: 5.1 s

    5.1 s

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

  • Real-user FCP: 4.0 s

    4.0 s

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

  • First Contentful Paint: 3.3 s

    3.3 s

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

  • Real-user INP: 305 ms

    305 ms

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

  • Real-user TTFB: 942 ms

    942 ms

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

  • Speed Index: 5.0 s

    5.0 s

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

  • Largest Contentful Paint: 3.3 s

    3.3 s

    Your largest element takes 3.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Welcome to AynAlfahad group”. Most of its time is element render delay (2.3 s).

  • Time to Interactive: 4.5 s

    4.5 s

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

  • 2 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    +1%

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

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.

  • Tap response (INP) got 35% faster for real visitors

    -35%

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 34 ms

    34 ms

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

Images and page weight

1 to fix33
  • Page weight: 39.0 MB in 64 requests

    39.0 MB

    Your homepage downloads 39.0 MB in 64 requests on a phone: images 26.2 MB (37), media 12.2 MB (1) and scripts 388 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • About 11.1 g of CO₂ per visit

    11.06 g

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

Accessibility

6 to fixGoogle 7683
  • Documents must have <title> element to aid in navigation (1 element)

    Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

  • 26 buttons without a name

    26 buttons have no accessible name, so screen readers announce just “button”.

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

  • 34 text elements with low contrast

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

1 checks passed
  • 18 automated accessibility rules passed

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

SEO

9 to fixGoogle 6747
  • No page title

    Your page has no <title>, so Google has to invent the blue link in search results.

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

  • 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://aynalfahad.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

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

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • 3 links with vague text

    3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

1 checks passed
  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

AI search readiness

1 to fix69
  • 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://aynalfahad.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.

Best practices

1 to fixGoogle 9692
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 401 ()”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix33
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

  • Only about 0 words

    The homepage has only about 0 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

1 checks passed
  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

  • 3 other companies contacted

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

Upkeep, stack and company

Stack

Hosting
Cloudflare

Company

Headquarters
London

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on aynalfahad.com, including 16 speed issues, 9 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

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