Website review, no card needed
alsayegh.com website review
Visit site (opens in a new tab)Reviewed 4 November 202645 issues · 79 checks
This review found 45 issues worth fixing on alsayegh.com, 18 of them high impact, across 79 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
68DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.6 s |
| May 23, 2026 | 2.5 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.5 s |
| Jun 27, 2026 | 2.6 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.6 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.5 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.5 s |
| Aug 22, 2026 | 2.7 s |
| Aug 29, 2026 | 3.1 s |
| Sep 5, 2026 | 3.2 s |
| Sep 12, 2026 | 3.3 s |
| Sep 19, 2026 | 3.9 s |
| Sep 26, 2026 | 4.2 s |
| Oct 3, 2026 | 4.2 s |
| Oct 10, 2026 | 4.2 s |
| Oct 17, 2026 | 4.4 s |
| Oct 24, 2026 | 4.2 s |
| Oct 31, 2026 | 4.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 90 ms |
| May 23, 2026 | 89 ms |
| May 30, 2026 | 89 ms |
| Jun 6, 2026 | 90 ms |
| Jun 13, 2026 | 91 ms |
| Jun 20, 2026 | 90 ms |
| Jun 27, 2026 | 88 ms |
| Jul 4, 2026 | 88 ms |
| Jul 11, 2026 | 87 ms |
| Jul 18, 2026 | 90 ms |
| Jul 25, 2026 | 92 ms |
| Aug 1, 2026 | 92 ms |
| Aug 8, 2026 | 94 ms |
| Aug 15, 2026 | 93 ms |
| Aug 22, 2026 | 95 ms |
| Aug 29, 2026 | 114 ms |
| Sep 5, 2026 | 139 ms |
| Sep 12, 2026 | 187 ms |
| Sep 19, 2026 | 546 ms |
| Sep 26, 2026 | 692 ms |
| Oct 3, 2026 | 669 ms |
| Oct 10, 2026 | 564 ms |
| Oct 17, 2026 | 445 ms |
| Oct 24, 2026 | 367 ms |
| Oct 31, 2026 | 367 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
Use efficient cache lifetimes
3.1 s · 3.9 MB55 files are served with short cache lifetimes, so returning visitors download them again (3.9 MB).
46,337 HTML elements
The page has 46,337 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
1.6 s · 2.9 MB26 images could be 2.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.6 s faster on a phone.
Reduce unused JavaScript
3.8 s · 696 KiBAbout 696 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.8 s faster on a phone.
Render-blocking requests
2.9 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.9 s.
Mobile performance score: 46
46/100Your mobile performance score is 46. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, openai.com and Cookiebot and others), adding 1.5 MB and 743 ms of main-thread time.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 745 ms. During a long task the page ignores taps.
Google Tag Manager adds 310 ms
310 msGoogle Tag Manager costs a phone 310 ms of main-thread work and 505 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.
Main-thread work: 2.9 s
A phone's processor spends 2.9 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Cookiebot adds 119 ms
119 msCookiebot costs a phone 119 ms of main-thread work and 447 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.
Google CDN adds 81 ms
81 msGoogle CDN costs a phone 81 ms of main-thread work and 380 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.
Reduce unused CSS
150 ms · 52 KiBAbout 52 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.
Document request latency
23 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
Minify CSS
7 KiB7 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.
1 checks passed
Server response: 210 ms
210 msYour server sent the HTML in 210 ms, well inside Google's 600 ms guideline.
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 LCP: 4.6 s
4.6 sReal visitors wait 4.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 720 ms
720 msReal visitors wait 720 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 3.1 s
3.1 sReal visitors see the first content after 3.1 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 26.7 s
26.7 sYour largest element takes 26.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to personalise content and ads, to provide s…”.
Time to Interactive: 27.7 s
27.7 sThe page becomes fully interactive after 27.7 s. Good is under 3.8 s.
Speed Index: 12.5 s
12.5 sVisually, the page fills in at 12.5 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.3 s
3.3 sThe first text or image appears after 3.3 s on a phone. Good is under 1.8 s.
Tap response (INP) got 310% slower for real visitors
+310%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 90 ms to 367 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 65% slower for real visitors
+65%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.6 s to 4.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 1.4 s
1.4 sReal visitors wait 1.4 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 536 ms
536 msScripts block taps and scrolling for 536 ms in total while the page loads. Good is under 200 ms.
33 images without width and height
33 images have no width and height attributes, so the layout jumps as each one loads.
2 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 5.3 MB in 88 requests
5.3 MBYour homepage downloads 5.3 MB in 88 requests on a phone: images 3.6 MB (49), scripts 1.6 MB (18) and stylesheets 59 KiB (6). Under 2 MB keeps phones on slow connections fast.
About 1.5 g of CO₂ per visit
1.51 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.51 g of CO₂e: 181.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
12 images without alt text
12 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (15 elements)
All page content should be contained by landmarks: 15 elements on the page fail this check, rated moderate by axe-core.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
1 checks passed
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 4 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.
Title is short (8 characters)
Your title is only 8 characters: “Alsayegh”. 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://alsayegh.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at alsayegh.com/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 set, so this is minor.
31 internal links, 3 external
The homepage links to 31 pages on alsayegh.com and 3 external pages.
2 checks passed
Meta description: 90 characters
Your meta description is 90 characters: “Guiding You Through this Ever-changing Digitized World as Your Partner. Let's Get in Touch”.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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://alsayegh.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.
1 checks passed
Text is in the HTML
Your server sends the page's text in the HTML (187 words), so crawlers that don't run JavaScript still read it.
Other pages
16 pages share a title
/, https://alsayegh.com/services/events, https://alsayegh.com/services/conferences, https://alsayegh.com/services/branding, https://alsayegh.com/services/video and https://alsayegh.com/services/socialmedia and 10 others all use the title “Alsayegh”. Search engines can't tell which page to show for a search, so each competes with the others.
15 pages share a meta description
https://alsayegh.com/services/events, https://alsayegh.com/services/conferences, https://alsayegh.com/services/branding, https://alsayegh.com/services/video, https://alsayegh.com/services/socialmedia and https://alsayegh.com/services/influencer_marketing and 9 others use the same meta description. A description written for each page earns more clicks.
15 pages without an H1
https://alsayegh.com/services/events, https://alsayegh.com/services/conferences, https://alsayegh.com/services/branding, https://alsayegh.com/services/video, https://alsayegh.com/services/socialmedia and https://alsayegh.com/services/influencer_marketing and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 pages with very little text
https://alsayegh.com/services/events, https://alsayegh.com/services/conferences, https://alsayegh.com/services/branding, https://alsayegh.com/services/video, https://alsayegh.com/services/socialmedia and https://alsayegh.com/services/influencer_marketing and 9 others 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 25 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
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”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
36 of 39 tappable elements near the top are at least 24 px.
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.
Thin social proof
Social proof on the homepage: 14 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
Only about 235 words
The homepage has only about 235 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
4 checks passed
1 call to action
The homepage has 1 call to action, for example “Contact”.
1 short form
A short form (4 fields at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Hotjar.
Direct contact links
Visitors can reach you directly: 5 phone links and 1 email link.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Hotjar (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
6 cookies set on arrival
6Opening the homepage sets 6 cookies (measured from a US location before any click).
19 other companies contacted
Loading the homepage contacts 19 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) loads with the page.
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 alsayegh.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager | Hotjar
- Hosting
- Buzinessware FZCO
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 alsayegh.com, including 25 speed issues, 6 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.