Website review, no card needed
almosafer.com website review
Visit site (opens in a new tab)Reviewed 4 November 202638 issues · 83 checks
This review found 38 issues worth fixing on almosafer.com, 12 of them high impact, across 83 checks. The most urgent: reduce unused JavaScript. 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 | 5.0 s |
| May 23, 2026 | 5.0 s |
| May 30, 2026 | 5.2 s |
| Jun 6, 2026 | 5.7 s |
| Jun 13, 2026 | 6.2 s |
| Jun 20, 2026 | 6.4 s |
| Jun 27, 2026 | 6.5 s |
| Jul 4, 2026 | 6.3 s |
| Jul 11, 2026 | 5.9 s |
| Jul 18, 2026 | 5.4 s |
| Jul 25, 2026 | 5.3 s |
| Aug 1, 2026 | 5.2 s |
| Aug 8, 2026 | 5.2 s |
| Aug 15, 2026 | 5.2 s |
| Aug 22, 2026 | 5.1 s |
| Aug 29, 2026 | 5.2 s |
| Sep 5, 2026 | 5.1 s |
| Sep 12, 2026 | 5.0 s |
| Sep 19, 2026 | 4.9 s |
| Sep 26, 2026 | 4.7 s |
| Oct 3, 2026 | 4.7 s |
| Oct 10, 2026 | 4.6 s |
| Oct 17, 2026 | 4.4 s |
| Oct 24, 2026 | 4.2 s |
| Oct 31, 2026 | 3.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 400 ms |
| May 23, 2026 | 421 ms |
| May 30, 2026 | 440 ms |
| Jun 6, 2026 | 472 ms |
| Jun 13, 2026 | 512 ms |
| Jun 20, 2026 | 525 ms |
| Jun 27, 2026 | 530 ms |
| Jul 4, 2026 | 528 ms |
| Jul 11, 2026 | 521 ms |
| Jul 18, 2026 | 511 ms |
| Jul 25, 2026 | 500 ms |
| Aug 1, 2026 | 493 ms |
| Aug 8, 2026 | 482 ms |
| Aug 15, 2026 | 477 ms |
| Aug 22, 2026 | 474 ms |
| Aug 29, 2026 | 474 ms |
| Sep 5, 2026 | 476 ms |
| Sep 12, 2026 | 482 ms |
| Sep 19, 2026 | 497 ms |
| Sep 26, 2026 | 507 ms |
| Oct 3, 2026 | 526 ms |
| Oct 10, 2026 | 531 ms |
| Oct 17, 2026 | 512 ms |
| Oct 24, 2026 | 487 ms |
| Oct 31, 2026 | 464 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.5 s
1.0 s
1.6 s
2.1 s
2.6 s
3.1 s
3.7 s
4.2 s
Speed
Reduce unused JavaScript
5.6 s · 1.6 MBAbout 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.6 s faster on a phone.
Mobile performance score: 35
35/100Your mobile performance score is 35. 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, Amplitude Mobile Analytics and Usercentrics CMP and others), adding 2.0 MB and 1.2 s of main-thread time.
Google Tag Manager adds 947 ms
947 msGoogle Tag Manager costs a phone 947 ms of main-thread work and 1.4 MB 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.
Avoid multiple page redirects
764 msThe page goes through 1 redirect before it starts loading, costing about 764 ms. Link and advertise the final URL directly.
Use efficient cache lifetimes
450 ms · 241 KiB20 files are served with short cache lifetimes, so returning visitors download them again (241 KiB).
Improve image delivery
150 ms · 325 KiB12 images could be 325 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
19 long tasks on the main thread
19 long tasks block the main thread while loading, the longest for 400 ms. During a long task the page ignores taps.
Main-thread work: 4.0 s
A phone's processor spends 4.0 s on main-thread work while loading, 2.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,832 HTML elements
The page has 1,832 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Document request latency
200 msThe HTML itself could arrive about 200 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Legacy JavaScript
55 KiBPolyfills for old browsers add 55 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.
1 checks passed
Server response: 43 ms
43 msYour server sent the HTML in 43 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.
Largest Contentful Paint: 19.4 s
19.4 sYour largest element takes 19.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Cairo”.
Time to Interactive: 25.9 s
25.9 sThe page becomes fully interactive after 25.9 s. Good is under 3.8 s.
Speed Index: 11.7 s
11.7 sVisually, the page fills in at 11.7 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.2 s
1.2 sScripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.6 s
3.6 sThe first text or image appears after 3.6 s on a phone. Good is under 1.8 s.
Real-user LCP: 3.1 s
3.1 sReal visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 269 ms
269 msReal visitors wait 269 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.4 s
2.4 sReal visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.8 s
1.8 sReal visitors wait 1.8 s for your server to start answering (75th percentile). Good is under 800 ms.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 16% slower for real visitors
+16%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 400 ms to 464 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.
Largest content (LCP) got 19% faster for real visitors
-19%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 5.0 s to 3.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.0 MB in 132 requests
5.0 MBYour homepage downloads 5.0 MB in 132 requests on a phone: scripts 3.3 MB (55), images 1.2 MB (41) and HTML 356 KiB (2). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
images 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).
About 1.4 g of CO₂ per visit
1.42 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.42 g of CO₂e: 170.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
23 text elements with low contrast
23 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
24 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 27 WCAG 2.2 A/AA and best-practice rules on the phone render: 24 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (69 characters)
Your title is 69 characters, so Google will cut it off around 60: “Almosafer: Flights, Hotels, Activities, Transfers, Car Rentals & More”.
Meta description is long (178 characters)
Your meta description is 178 characters; Google truncates after about 160, so the end of your pitch is cut.
No XML sitemap
No XML sitemap at https://global.almosafer.com/en/travel/sitemap/sitemap.xml, so Google discovers your pages only by following links.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
292 internal links, 19 external
The homepage links to 292 pages on almosafer.com and 19 external pages.
5 checks passed
One H1 headline
Your main headline reads: “The entire world awaits you!”.
Canonical URL set
The canonical URL is https://global.almosafer.com/en.
Structured data in place
Structured data found: FAQPage and Organization.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
AI search readiness
No llms.txt
There is no https://global.almosafer.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.
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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (2,094 words), so crawlers that don't run JavaScript still read it.
Other pages
6 pages share 2 titles
https://global.almosafer.com/en and https://global.almosafer.com/en/services all use the title “Almosafer: Flights, Hotels, Activities, Transfers, Car Rentals & More”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
4 pages share a meta description
https://global.almosafer.com/en/activities/categories/108, https://global.almosafer.com/en/activities/categories/94, https://global.almosafer.com/en/activities/categories/111 and https://global.almosafer.com/en/activities/categories/115 use the same meta description. A description written for each page earns more clicks.
7 pages without an H1
https://global.almosafer.com/en/activities/categories/108, https://global.almosafer.com/en/activities/categories/94, https://global.almosafer.com/en/activity/details/1177, https://global.almosafer.com/en/activities/categories/111, https://global.almosafer.com/en/activity/details/1398 and https://global.almosafer.com/en/activities/categories/115 and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.
4 pages slow to respond
https://global.almosafer.com/en/activities/categories/108, https://global.almosafer.com/en/activities/categories/94, https://global.almosafer.com/en/activity/details/1177 and https://global.almosafer.com/en/activities/categories/111 took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 199 found) and read each the way a search engine does.
5 checks passed
Linked pages load
7 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 7 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 7 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 “Cannot read properties of undefined (reading 'register')”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
38 of 46 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.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
About 603 words of copy
The homepage carries about 603 words of visible text.
5 checks passed
1 call to action
The homepage has 1 call to action, for example “Contact Us”.
Social proof on the page
Social proof on the homepage: 13 testimonial or review blocks, 3 customer or partner logos, a star rating, 2 trust badges and “10M+ downloads”.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Amplitude, Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (Usercentrics) 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).
11 other companies contacted
Loading the homepage contacts 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Usercentrics
A consent management tool (Usercentrics) 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 almosafer.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
- Next.js
- Analytics
- Google Tag Manager
- Hosting
- Cloudflare
Hiring
- Hiring
- 10 open roles
- Job board
- smartrecruiters
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 almosafer.com, including 21 speed issues, 4 SEO issues and 1 conversion gap. 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.