Website review, no card needed
alfaisal.edu website review
Visit site (opens in a new tab)Reviewed 31 October 202645 issues · 88 checks
This review found 45 issues worth fixing on alfaisal.edu, 21 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.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
71CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.8 s |
| May 16, 2026 | 2.9 s |
| May 23, 2026 | 2.9 s |
| May 30, 2026 | 2.8 s |
| Jun 6, 2026 | 2.7 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.5 s |
| Jun 27, 2026 | 2.5 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.5 s |
| Aug 1, 2026 | 2.9 s |
| Aug 8, 2026 | 2.9 s |
| Aug 15, 2026 | 2.9 s |
| Aug 22, 2026 | 2.8 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.8 s |
| Sep 12, 2026 | 2.9 s |
| Sep 19, 2026 | 3.0 s |
| Sep 26, 2026 | 3.0 s |
| Oct 3, 2026 | 2.8 s |
| Oct 10, 2026 | 2.7 s |
| Oct 17, 2026 | 2.8 s |
| Oct 24, 2026 | 3.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 110 ms |
| May 16, 2026 | 112 ms |
| May 23, 2026 | 110 ms |
| May 30, 2026 | 107 ms |
| Jun 6, 2026 | 106 ms |
| Jun 13, 2026 | 107 ms |
| Jun 20, 2026 | 107 ms |
| Jun 27, 2026 | 107 ms |
| Jul 4, 2026 | 104 ms |
| Jul 11, 2026 | 102 ms |
| Jul 18, 2026 | 102 ms |
| Jul 25, 2026 | 97 ms |
| Aug 1, 2026 | 105 ms |
| Aug 8, 2026 | 104 ms |
| Aug 15, 2026 | 105 ms |
| Aug 22, 2026 | 104 ms |
| Aug 29, 2026 | 99 ms |
| Sep 5, 2026 | 109 ms |
| Sep 12, 2026 | 112 ms |
| Sep 19, 2026 | 115 ms |
| Sep 26, 2026 | 114 ms |
| Oct 3, 2026 | 106 ms |
| Oct 10, 2026 | 103 ms |
| Oct 17, 2026 | 107 ms |
| Oct 24, 2026 | 106 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
How it loaded on a phone
1.5 s
3.1 s
4.6 s
6.1 s
7.7 s
9.2 s
10.7 s
12.2 s
Speed
Use efficient cache lifetimes
7.0 s · 27.6 MB61 files are served with short cache lifetimes, so returning visitors download them again (27.6 MB).
Improve image delivery
1.3 s · 7.5 MB27 images could be 7.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.3 s faster on a phone.
Render-blocking requests
6.4 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 6.4 s.
Document request latency
5.4 s · 148 KiBThe HTML itself could arrive about 5.4 s sooner: redirects, a slow server response or missing compression delay everything after it.
Reduce initial server response time
5.4 sReduce initial server response time. Google estimates savings of 5.4 s on a phone.
Reduce unused CSS
4.3 s · 845 KiBAbout 845 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 4.3 s faster on a phone.
Server response: 5.5 s
5.5 sYour server takes 5.5 s to send the HTML. Google recommends under 600 ms; everything else waits for it.
Reduce unused JavaScript
300 ms · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Mobile performance score: 55
55/100Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.
Minify CSS
750 ms · 128 KiB128 KiB could be saved by minifying CSS.
1,624 HTML elements
The page has 1,624 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
4 third-party services on the page
4 third-party services load with your homepage (Google Tag Manager, Clarity and Adobe TypeKit and others), adding 372 KiB and 152 ms of main-thread time.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 162 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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.
1 checks passed
Main-thread work: 1.5 s
A phone's processor spends 1.5 s on main-thread work while loading, 635 ms of it running JavaScript. That is comfortably low.
Core Web Vitals
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 FCP: 3.7 s
3.7 sReal visitors see the first content after 3.7 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 8.1 s
8.1 sThe first text or image appears after 8.1 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 11.9 s
11.9 sYour largest element takes 11.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is time to first byte (5.5 s).
Speed Index: 25.8 s
25.8 sVisually, the page fills in at 25.8 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 38.2 s
38.2 sThe page becomes fully interactive after 38.2 s. Good is under 3.8 s.
Real-user LCP: 3.9 s
3.9 sReal visitors wait 3.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user TTFB: 1.3 s
1.3 sReal visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 110 ms to 106 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.8 s to 3.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 126 ms
126 msReal visitors wait 126 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Total Blocking Time: 89 ms
89 msScripts block the page for only 89 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 28.2 MB in 79 requests
28.2 MBYour homepage downloads 28.2 MB in 79 requests on a phone: media 15.1 MB (7), images 10.1 MB (47) and scripts 1.7 MB (6). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
6ae1ad55ac7e6148452536.jpg weighs 5.4 MB. On a phone connection a single image that size takes seconds.
9 images far larger than shown
4.9 MB9 images are downloaded at several times the size a phone draws them, for example 6ae1ad55ac7e6148452536.jpg at 1,920 px wide, shown at 302 px. Resized copies would save about 4.9 MB.
28 images in older formats
28 images (8.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.
22 images below the first screen load straight away
22 images further down the page (7.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 8.0 g of CO₂ per visit
7.99 gBy the Sustainable Web Design model, a visit to your homepage emits about 7.99 g of CO₂e: 958.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
<svg> elements with an img or image role must have alternative text (11 elements)
<svg> elements with an img or image role must have alternative text: 11 elements on the page fail this check, rated serious by axe-core.
All page content should be contained by landmarks (12 elements)
All page content should be contained by landmarks: 12 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
11 links without text
11 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.
Headings skip levels
Headings skip levels (h2 → h4), 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. (1 element).
2 checks passed
Every image has alt text
All 42 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
robots.txt blocks all crawlers
Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.
Blocked from indexing
Google's crawler is blocked from indexing this page.
Title is long (74 characters)
Your title is 74 characters, so Google will cut it off around 60: “Alfaisal University | Alfaisal University, Riyadh, Kingdom of Saudi Arabia”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
9 H1 headlines
There are 9 <h1> headlines (“Discover Your Future with Alfaisal University”, “Alfaisal University Stands Out” and “Why Alfaisal?”). One clear main headline is easier for people and search engines.
Meta description is long (161 characters)
Your meta description is 161 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
4 links crawlers can't follow
4 links have no real href, so search engines can't follow them.
47 internal links, 135 external
The homepage links to 47 pages on alfaisal.edu and 135 external pages.
2 checks passed
Canonical URL set
The canonical URL is https://www.alfaisal.edu/en/.
XML sitemap found
Your XML sitemap is reachable at https://www.alfaisal.edu/sitemap.xml.
AI search readiness
robots.txt blocks 6 AI answer engine crawlers
6 of 6Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.
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.alfaisal.edu/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.
Opted out of AI training for 5 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.
1 checks passed
Text is in the HTML
Your server sends the page's text in the HTML (1,069 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page with very little text
https://www.alfaisal.edu/ar has 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.
1 page slow to respond
https://www.alfaisal.edu/ar took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 26 found) and read each the way a search engine does.
7 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
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
11 small tap targets
11 of 35 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 904 words of copy
The homepage carries about 904 words of visible text.
4 checks passed
6 calls to action
The homepage has 6 calls to action, for example “Contact Us”, “Apply” and “Schedule on Campus Visit”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 6 customer or partner logos, 1 trust badge and “5,900+ Students”.
Analytics in place
Analytics detected: Google Analytics and Microsoft Clarity.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Microsoft Clarity (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
4Opening 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 alfaisal.edu, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Saudinetstc
Company
- Founded
- 2002
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 45 issues on alfaisal.edu, including 20 speed issues, 8 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.