Website review, no card needed

afaq.edu.pk logo

afaq.edu.pk website review

Visit site (opens in a new tab)Reviewed 1 November 202634 issues · 83 checks

This review found 34 issues worth fixing on afaq.edu.pk, 14 of them high impact, across 83 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.8 s3.3 sMay 9Oct 243.7 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.4 s
May 16, 20263.4 s
May 23, 20263.5 s
May 30, 20263.6 s
Jun 6, 20263.7 s
Jun 13, 20263.7 s
Jun 20, 20263.7 s
Jun 27, 20263.6 s
Jul 4, 20263.6 s
Jul 11, 20263.6 s
Jul 18, 20263.4 s
Jul 25, 20263.5 s
Aug 1, 20263.4 s
Aug 8, 20263.3 s
Aug 15, 20263.4 s
Aug 22, 20263.4 s
Aug 29, 20263.4 s
Sep 5, 20263.4 s
Sep 12, 20263.4 s
Sep 19, 20263.4 s
Sep 26, 20263.5 s
Oct 3, 20263.6 s
Oct 10, 20263.6 s
Oct 17, 20263.7 s
Oct 24, 20263.7 s
Real-visitor tap response (INP)75th percentile, phones
210 ms182 msMay 9Oct 24190 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026205 ms
May 16, 2026205 ms
May 23, 2026207 ms
May 30, 2026206 ms
Jun 6, 2026206 ms
Jun 13, 2026207 ms
Jun 20, 2026202 ms
Jun 27, 2026198 ms
Jul 4, 2026194 ms
Jul 11, 2026188 ms
Jul 18, 2026185 ms
Jul 25, 2026185 ms
Aug 1, 2026185 ms
Aug 8, 2026186 ms
Aug 15, 2026185 ms
Aug 22, 2026185 ms
Aug 29, 2026188 ms
Sep 5, 2026186 ms
Sep 12, 2026186 ms
Sep 19, 2026187 ms
Sep 26, 2026186 ms
Oct 3, 2026186 ms
Oct 10, 2026186 ms
Oct 17, 2026189 ms
Oct 24, 2026190 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 afaq.edu.pk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. afaq.edu.pk at 0.7 s0.7 s
  2. afaq.edu.pk at 1.4 s1.4 s
  3. afaq.edu.pk at 2.2 s2.2 s
  4. afaq.edu.pk at 2.9 s2.9 s
  5. afaq.edu.pk at 3.6 s3.6 s
  6. afaq.edu.pk at 4.3 s4.3 s
  7. afaq.edu.pk at 5.0 s5.0 s
  8. afaq.edu.pk at 5.8 s5.8 s

Speed

8 to fix62
  • Render-blocking requests

    4.8 s

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

  • Reduce unused JavaScript

    3.3 s · 599 KiB

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

  • Use efficient cache lifetimes

    850 ms · 157 KiB

    91 files are served with short cache lifetimes, so returning visitors download them again (157 KiB).

  • Mobile performance score: 62

    62/100

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

  • Reduce unused CSS

    750 ms · 146 KiB

    About 146 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • Minify JavaScript

    600 ms · 107 KiB

    107 KiB could be saved by minifying JavaScript.

  • Font display

    550 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 550 ms).

  • Google Maps adds 103 ms

    103 ms

    Google Maps costs a phone 103 ms of main-thread work and 355 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.

  • Legacy JavaScript

    150 ms · 12 KiB

    Polyfills for old browsers add 12 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 2 third-party services on the page

    2 third-party services load with your homepage (Google Maps and Google Fonts), adding 426 KiB and 104 ms of main-thread time.

  • 2 long tasks on the main thread

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

  • Improve image delivery

    17 KiB

    1 image could be 17 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Minify CSS

    7 KiB

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

2 checks passed
  • Main-thread work: 1.6 s

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

  • Server response: 309 ms

    309 ms

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

Core Web Vitals

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

    4.3 s

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

  • Real-user FCP: 3.0 s

    3.0 s

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

  • Largest Contentful Paint: 11.6 s

    11.6 s

    Your largest element takes 11.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Complete Educational Solutions For Schools With Nationwide …”. Most of its time is element render delay (4.9 s).

  • Time to Interactive: 11.7 s

    11.7 s

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

  • Speed Index: 8.2 s

    8.2 s

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

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • Real-user INP: 213 ms

    213 ms

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

  • Real-user TTFB: 1.4 s

    1.4 s

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

  • Tap response (INP) held steady for real visitors

    -8%

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

  • Largest content (LCP) held steady for real visitors

    +7%

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

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

  • Cumulative Layout Shift: 0.001

    0.001

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

  • Total Blocking Time: 16 ms

    16 ms

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

Images and page weight

1 to fix90
  • 1 image far larger than shown

    150 KiB

    1 image is downloaded at several times the size a phone draws it, for example AFAQ-Logo-PNG--400x477.png at 390 px wide, shown at 45 px. Resized copies would save about 150 KiB.

  • 2 images in older formats

    2 images (248 KiB) 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.

  • About 0.5 g of CO₂ per visit

    0.53 g

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

2 checks passed
  • Page weight: 1.9 MB in 112 requests

    1.9 MB

    Your homepage downloads 1.9 MB in 112 requests on a phone: scripts 1.1 MB (55), images 312 KiB (5) and stylesheets 268 KiB (42). That is a lean page.

  • Images load when needed

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

Accessibility

8 to fixGoogle 7685
  • 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.

  • 5 tap targets too small

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

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

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

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

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

  • 2 links without text

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

2 checks passed
  • Every image has alt text

    All 7 images in the HTML carry an alt attribute.

  • 27 automated accessibility rules passed

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

SEO

3 to fixGoogle 9277
  • 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 social preview image

    No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 93 internal links, 38 external

    The homepage links to 93 pages on afaq.edu.pk and 38 external pages.

5 checks passed
  • Title: 49 characters

    Your title is a healthy 49 characters: “AFAQ - Complete Educational Solutions For Schools”.

  • Canonical URL set

    The canonical URL is https://afaq.edu.pk/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://afaq.edu.pk/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://afaq.edu.pk/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.

3 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: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, description and contact details; sameAs (social profiles) would complete it.

  • Text is in the HTML

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

Other pages

2 to fix90
  • 15 pages without a meta description

    https://afaq.edu.pk/contact-us, https://afaq.edu.pk/introduction, https://afaq.edu.pk/ceo-message, https://afaq.edu.pk/board-of-directors, https://afaq.edu.pk/introduction/corporate-information and https://afaq.edu.pk/annual-reports and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 9 pages without an H1

    https://afaq.edu.pk/shop, https://afaq.edu.pk/category/textbooks, https://afaq.edu.pk/category/textbooks/sun-series-ncp, https://afaq.edu.pk/category/textbooks/rising-sun-series, https://afaq.edu.pk/category/textbooks/iqbal-series-new-edition and https://afaq.edu.pk/category/textbooks/iqbal-series and 3 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 52 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
  • 7 small tap targets

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

  • Missing source maps

    Large scripts ship without source maps.

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 fix80
  • Thin social proof

    Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

    The homepage carries about 487 words of visible text.

3 checks passed
  • Clear next step on the first screen

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

  • 7 calls to action

    The homepage has 7 calls to action, for example “Contact Us” and “Shop Now”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

Privacy and tracking

  • 7 cookies set on arrival

    7

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

  • 4 other companies contacted

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

Upkeep, stack and company

  • The footer still says © 2023.

Stack

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
Hosting
Hostinger

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on afaq.edu.pk, including 17 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