Website review, no card needed
beam.co.ae website review
Visit site (opens in a new tab)Reviewed 3 November 202632 issues · 76 checks
This review found 32 issues worth fixing on beam.co.ae, 7 of them high impact, across 76 checks. The most urgent: render-blocking requests. 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
82BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 4.0 s |
| May 23, 2026 | 3.8 s |
| May 30, 2026 | 4.0 s |
| Jun 6, 2026 | 3.8 s |
| Jun 13, 2026 | 3.9 s |
| Jun 20, 2026 | 3.8 s |
| Jun 27, 2026 | 3.5 s |
| Jul 4, 2026 | 3.2 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 110 ms |
| May 23, 2026 | 110 ms |
| May 30, 2026 | 103 ms |
| Jun 6, 2026 | 105 ms |
| Jun 13, 2026 | 105 ms |
| Jun 20, 2026 | 104 ms |
| Jun 27, 2026 | 111 ms |
| Jul 4, 2026 | 117 ms |
| Jul 11, 2026 | 128 ms |
| Jul 18, 2026 | 153 ms |
| Jul 25, 2026 | 148 ms |
| Aug 1, 2026 | 157 ms |
| Aug 8, 2026 | 157 ms |
| Aug 15, 2026 | 145 ms |
| Aug 22, 2026 | 172 ms |
| Aug 29, 2026 | 160 ms |
| Sep 5, 2026 | 152 ms |
| Sep 12, 2026 | 156 ms |
| Sep 19, 2026 | 147 ms |
| Sep 26, 2026 | 147 ms |
| Oct 3, 2026 | 159 ms |
| Oct 10, 2026 | 141 ms |
| Oct 17, 2026 | 145 ms |
| Oct 24, 2026 | 141 ms |
| Oct 31, 2026 | 145 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
Speed
Render-blocking requests
1.1 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 73
73/100Your mobile performance score is 73. Pages that score under 90 lose visitors before the first paint.
Main-thread work: 3.4 s
A phone's processor spends 3.4 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
302 KiB12 images could be 302 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 190 ms. During a long task the page ignores taps.
Reduce unused JavaScript
44 KiBAbout 44 KiB of JavaScript is downloaded but never used on this page.
Legacy JavaScript
14 KiBPolyfills for old browsers add 14 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
Server response: 212 ms
212 msYour server sent the HTML in 212 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 11.6 s
11.6 sVisually, the page fills in at 11.6 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 4.5 s
4.5 sYour largest element takes 4.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Banner 1”. Most of its time is resource load duration (2.0 s).
Tap response (INP) got 30% slower for real visitors
+30%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 110 ms to 145 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Time to Interactive: 5.6 s
5.6 sThe page becomes fully interactive after 5.6 s. Good is under 3.8 s.
First Contentful Paint: 1.9 s
1.9 sThe first text or image appears after 1.9 s on a phone. Good is under 1.8 s.
7 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.3 s
1.3 sReal visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 63% faster for real visitors
-63%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 4.0 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 80 ms
80 msScripts block the page for only 80 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.002
0.002The layout barely moves while loading (CLS 0.002, good is under 0.1).
Images and page weight
An image on the first screen is lazy-loaded
image is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
1 image below the first screen load straight away
1 image further down the page (21 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.3 g of CO₂ per visit
0.33 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.33 g of CO₂e: 39.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 1.2 MB in 71 requests
1.2 MBYour homepage downloads 1.2 MB in 71 requests on a phone: images 654 KiB (31), scripts 354 KiB (21) and fonts 110 KiB (5). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Elements must only use permitted ARIA attributes (1 element)
Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
All page content should be contained by landmarks (18 elements)
All page content should be contained by landmarks: 18 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.
5 links without text
5 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.
2 checks passed
Every image has alt text
All 65 images in the HTML carry an alt attribute.
37 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
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.
Meta description is short (55 characters)
Your meta description is only 55 characters: “of Inspiring Leaders with Faith, Knowledge & Innovation”. 70 to 160 characters is enough to sell the click.
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 XML sitemap
No XML sitemap at https://beam.co.ae/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at beam.co.ae/robots.txt, the first file search crawlers ask for.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
13 internal links, 13 external
The homepage links to 13 pages on beam.co.ae and 13 external pages.
1 checks passed
Title: 55 characters
Your title is a healthy 55 characters: “of Inspiring Leaders with Faith, Knowledge & Innovation”.
AI search readiness
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://beam.co.ae/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 (423 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://beam.co.ae/contact-us has no meta description, so Google writes the search snippet from whatever text it finds.
12 pages without an H1
https://beam.co.ae/about-us/school-leadership-team, https://beam.co.ae/about-us/our-story, https://beam.co.ae/beam-schools, https://beam.co.ae/about-us/professional-learning-program, https://beam.co.ae/beam-schools/school-scholarship-programs and https://beam.co.ae/beam-schools/school-uniqueness and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://beam.co.ae/about-us/school-leadership-team, https://beam.co.ae/contact-us and https://beam.co.ae/news-&-media/blog 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.
4 pages slow to respond
https://beam.co.ae/about-us/our-story, https://beam.co.ae/beam-schools, https://beam.co.ae/about-us/professional-learning-program and https://beam.co.ae/beam-schools/school-scholarship-programs took over 3 s to send their HTML from our server.
12 internal pages checked
We fetched 12 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 12 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 12 pages that loaded have a <title>.
Best practices
2 distorted images
2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
11 of 11 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: “0 + Active Students”. 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.
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 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.
About 407 words of copy
The homepage carries about 407 words of visible text.
2 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “REGISTER INTEREST”.
3 calls to action
The homepage has 3 calls to action, for example “Register Interest” and “Register Your Interest”.
Privacy and tracking
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.
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 beam.co.ae, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
- Hosting
- Oracle Cloud
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on beam.co.ae, including 9 speed issues, 7 SEO issues and 3 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.