Website review, no card needed
alhassanllc.com website review
Visit site (opens in a new tab)Reviewed 30 October 202638 issues · 76 checks
This review found 38 issues worth fixing on alhassanllc.com, 17 of them high impact, across 76 checks. The most urgent: improve image delivery. 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
75CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.1 s |
| May 16, 2026 | 2.9 s |
| May 23, 2026 | 3.0 s |
| May 30, 2026 | 2.8 s |
| Jun 6, 2026 | 2.8 s |
| Jun 13, 2026 | 3.1 s |
| Jun 20, 2026 | 3.1 s |
| Jun 27, 2026 | 3.1 s |
| Jul 4, 2026 | 3.3 s |
| Jul 11, 2026 | 3.2 s |
| Jul 18, 2026 | 3.4 s |
| Jul 25, 2026 | 3.4 s |
| Aug 1, 2026 | 3.7 s |
| Aug 8, 2026 | 4.3 s |
| Aug 15, 2026 | 3.8 s |
| Aug 22, 2026 | 3.7 s |
| Aug 29, 2026 | 3.7 s |
| Sep 5, 2026 | 3.1 s |
| Sep 12, 2026 | 3.1 s |
| Sep 19, 2026 | 3.0 s |
| Sep 26, 2026 | 3.2 s |
| Oct 3, 2026 | 3.7 s |
| Oct 10, 2026 | 3.9 s |
| Oct 17, 2026 | 3.9 s |
| Oct 24, 2026 | 3.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Jun 27, 2026 | 96 ms |
| Jul 4, 2026 | 103 ms |
| Jul 11, 2026 | 124 ms |
| Jul 25, 2026 | 134 ms |
| Aug 1, 2026 | 120 ms |
| Aug 8, 2026 | 105 ms |
| Aug 15, 2026 | 99 ms |
| Aug 22, 2026 | 89 ms |
| Aug 29, 2026 | 111 ms |
| Sep 5, 2026 | 105 ms |
| Sep 12, 2026 | 109 ms |
| Sep 19, 2026 | 114 ms |
| Sep 26, 2026 | 113 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
0.6 s
1.2 s
1.8 s
2.4 s
3.0 s
3.6 s
4.2 s
4.8 s
Speed
Improve image delivery
10.7 s · 2.3 MB13 images could be 2.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 10.7 s faster on a phone.
Use efficient cache lifetimes
5.1 s · 1.5 MB55 files are served with short cache lifetimes, so returning visitors download them again (1.5 MB).
Render-blocking requests
1.1 s21 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 54
54/100Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.
Font display
900 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 900 ms).
1 third-party service on the page
1 third-party service load with your homepage (sucuri.net), adding 8 KiB and 24 ms of main-thread time.
Reduce unused CSS
24 KiBAbout 24 KiB of CSS is downloaded but never applied on this page.
Reduce unused JavaScript
21 KiBAbout 21 KiB of JavaScript is downloaded but never used on this page.
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.
2 checks passed
Main-thread work: 0.5 s
A phone's processor spends 0.5 s on main-thread work while loading, 175 ms of it running JavaScript. That is comfortably low.
Server response: 7 ms
7 msYour server sent the HTML in 7 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 FCP: 3.2 s
3.2 sReal visitors see the first content after 3.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.1 s
2.1 sReal visitors wait 2.1 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 13.4 s
13.4 sYour largest element takes 13.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Al-Hassan-Smart-WebsiteBanner-w1920x1280-eng”.
Speed Index: 9.5 s
9.5 sVisually, the page fills in at 9.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 13.4 s
13.4 sThe page becomes fully interactive after 13.4 s. Good is under 3.8 s.
Largest content (LCP) got 27% slower for real visitors
+27%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.1 s to 3.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.229
0.229The layout shifts by 0.229 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 96 ms to 113 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
2 images over 500 KB
2 images weigh 2.1 MB together. On a phone connection a single image that size takes seconds.
2 images far larger than shown
1.3 MB2 images are downloaded at several times the size a phone draws them, for example Al-Hassan-Smart-WebsiteBanner-w1920x1280-eng.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 1.3 MB.
Page weight: 3.7 MB in 56 requests
3.7 MBYour homepage downloads 3.7 MB in 56 requests on a phone: images 3.3 MB (17), fonts 214 KiB (3) and scripts 132 KiB (15). Under 2 MB keeps phones on slow connections fast.
6 images in older formats
6 images (2.4 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.
About 1.1 g of CO₂ per visit
1.05 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.05 g of CO₂e: 126.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
<svg> elements with an img or image role must have alternative text (1 element)
<svg> elements with an img or image role must have alternative text: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (17 elements)
All page content should be contained by landmarks: 17 elements on the page fail this check, rated moderate by axe-core.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h2 → h5 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 19 images in the HTML carry an alt attribute.
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (13 characters)
Your title is only 13 characters: “Al Hassan LLC”. 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.
2 H1 headlines
There are 2 <h1> headlines (“Al Hassan LLC” and “Al Hassan LLC”). One clear main headline is easier for people and search engines.
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.
4 links with vague text
4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
48 internal links, 1 external
The homepage links to 48 pages on alhassanllc.com and 1 external page.
3 checks passed
Canonical URL set
The canonical URL is http://alhassanllc.com/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at http://alhassanllc.com/wp-sitemap.xml.
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://alhassanllc.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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (433 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page points its canonical at the homepage
https://alhassanllc.com/home declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
2 pages share a title
/ and https://alhassanllc.com/home all use the title “Al Hassan LLC”. Search engines can't tell which page to show for a search, so each competes with the others.
15 pages without a meta description
https://alhassanllc.com/home, https://alhassanllc.com/our-history, https://alhassanllc.com/brands, https://alhassanllc.com/flowmax, https://alhassanllc.com/powerlink and https://alhassanllc.com/alishraqdb and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
11 pages without an H1
https://alhassanllc.com/our-history, https://alhassanllc.com/brands, https://alhassanllc.com/flowmax, https://alhassanllc.com/powerlink, https://alhassanllc.com/alishraqdb and https://alhassanllc.com/ah-db-classic and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://alhassanllc.com/brands, https://alhassanllc.com/ahe-loyalty-program and https://alhassanllc.com/airmax 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://alhassanllc.com/home, https://alhassanllc.com/flowmax, https://alhassanllc.com/ah-db-classic and https://alhassanllc.com/ah-db-smart took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 25 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
4 small tap targets
4 of 14 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 “Access to XMLHttpRequest at 'https://cdn.sucuri.net/badge/badge-godaddy.css' from origin 'https://alhassanllc.com' has …”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 320 words of copy
The homepage carries about 320 words of visible text.
1 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Contact Us”.
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 other company contacted
Loading the homepage contacts 1 host 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 alhassanllc.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Hosting
- Sucuri
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on alhassanllc.com, including 13 speed issues, 6 SEO issues and 4 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.