Website review, no card needed
flytaag.com website review
Visit site (opens in a new tab)Reviewed 17 November 202649 issues · 90 checks
This review found 49 issues worth fixing on flytaag.com, 26 of them high impact, across 90 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
60DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 3.4 s |
| Jun 6, 2026 | 3.4 s |
| Jun 13, 2026 | 3.4 s |
| Jun 20, 2026 | 3.4 s |
| Jun 27, 2026 | 3.3 s |
| Jul 4, 2026 | 3.4 s |
| Jul 11, 2026 | 3.4 s |
| Jul 18, 2026 | 3.4 s |
| Jul 25, 2026 | 3.5 s |
| Aug 1, 2026 | 3.6 s |
| Aug 8, 2026 | 3.7 s |
| Aug 15, 2026 | 3.8 s |
| Aug 22, 2026 | 3.8 s |
| Aug 29, 2026 | 3.8 s |
| Sep 5, 2026 | 3.8 s |
| Sep 12, 2026 | 3.8 s |
| Sep 19, 2026 | 3.8 s |
| Sep 26, 2026 | 3.9 s |
| Oct 3, 2026 | 4.1 s |
| Oct 10, 2026 | 4.4 s |
| Oct 17, 2026 | 4.8 s |
| Oct 24, 2026 | 5.4 s |
| Oct 31, 2026 | 6.3 s |
| Nov 7, 2026 | 6.2 s |
| Nov 14, 2026 | 6.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 444 ms |
| Jun 6, 2026 | 446 ms |
| Jun 13, 2026 | 446 ms |
| Jun 20, 2026 | 444 ms |
| Jun 27, 2026 | 442 ms |
| Jul 4, 2026 | 443 ms |
| Jul 11, 2026 | 444 ms |
| Jul 18, 2026 | 445 ms |
| Jul 25, 2026 | 447 ms |
| Aug 1, 2026 | 446 ms |
| Aug 8, 2026 | 446 ms |
| Aug 15, 2026 | 455 ms |
| Aug 22, 2026 | 473 ms |
| Aug 29, 2026 | 497 ms |
| Sep 5, 2026 | 521 ms |
| Sep 12, 2026 | 533 ms |
| Sep 19, 2026 | 543 ms |
| Sep 26, 2026 | 545 ms |
| Oct 3, 2026 | 546 ms |
| Oct 10, 2026 | 549 ms |
| Oct 17, 2026 | 547 ms |
| Oct 24, 2026 | 545 ms |
| Oct 31, 2026 | 537 ms |
| Nov 7, 2026 | 533 ms |
| Nov 14, 2026 | 532 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
Improve image delivery
40.5 s · 7.9 MB5 images could be 7.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 40.5 s faster on a phone.
Render-blocking requests
4.0 s30 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.0 s.
Reduce unused JavaScript
1.8 s · 305 KiBAbout 305 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.
Mobile performance score: 42
42/100Your mobile performance score is 42. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
3,705 HTML elements
The page has 3,705 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused CSS
750 ms · 126 KiBAbout 126 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, jQuery CDN and Google CDN and others), adding 734 KiB and 576 ms of main-thread time.
Google Tag Manager adds 368 ms
368 msGoogle Tag Manager costs a phone 368 ms of main-thread work and 506 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.
Minify JavaScript
300 ms · 47 KiB47 KiB could be saved by minifying JavaScript.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 171 ms. During a long task the page ignores taps.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Legacy JavaScript
24 KiBPolyfills for old browsers add 24 KiB JavaScript that modern phones do not need.
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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
2 checks passed
Main-thread work: 1.5 s
A phone's processor spends 1.5 s on main-thread work while loading, 673 ms of it running JavaScript. That is comfortably low.
Server response: 225 ms
225 msYour server sent the HTML in 225 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: 11.6 s
11.6 sReal visitors wait 11.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 529 ms
529 msReal visitors wait 529 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 8.9 s
8.9 sReal visitors see the first content after 8.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 7.6 s
7.6 sReal visitors wait 7.6 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 65.1 s
65.1 sYour largest element takes 65.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Luanda - Praia”.
Time to Interactive: 65.1 s
65.1 sThe page becomes fully interactive after 65.1 s. Good is under 3.8 s.
First Contentful Paint: 4.4 s
4.4 sThe first text or image appears after 4.4 s on a phone. Good is under 1.8 s.
Speed Index: 7.8 s
7.8 sVisually, the page fills in at 7.8 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.275
0.275The layout shifts by 0.275 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user CLS: 0.22
0.22For real visitors the layout shifts by 0.22 (75th percentile). Good is under 0.1.
Tap response (INP) got 20% slower for real visitors
+20%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 444 ms to 532 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 82% slower for real visitors
+82%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.4 s to 6.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
1 checks passed
Total Blocking Time: 187 ms
187 msScripts block the page for only 187 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 12.3 MB in 109 requests
12.3 MBYour homepage downloads 12.3 MB in 109 requests on a phone: images 11.1 MB (45), scripts 926 KiB (44) and HTML 162 KiB (1). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 9.5 MB together. On a phone connection a single image that size takes seconds.
7 images far larger than shown
8.1 MB7 images are downloaded at several times the size a phone draws them, for example CaboVerde3-1600x500.png at 3,200 px wide, shown at 390 px. Resized copies would save about 8.1 MB.
9 images in older formats
9 images (10.7 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.
5 images below the first screen load straight away
5 images further down the page (128 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 3.5 g of CO₂ per visit
3.50 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.50 g of CO₂e: 419.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
13 buttons without a name
13 buttons have no accessible name, so screen readers announce just “button”.
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
13 tap targets too small
13 tap targets are too small or too close together to hit reliably with a finger.
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Orphan list items
Some list items are not inside a list.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (44 elements)
All page content should be contained by landmarks: 44 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 form fields without a label
6 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 59 images in the HTML carry an alt attribute.
43 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: 43 passed and 9 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
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://flytaag.com/sitemap.xml, so Google discovers your pages only by following links.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
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.
165 internal links, 27 external
The homepage links to 165 pages on flytaag.com and 27 external pages.
5 checks passed
Meta description: 153 characters
Your meta description is 153 characters: “Travel to more than 35 destinations in Africa, Europe, America and Asia. Online reservations and international flights.…”.
One H1 headline
Your main headline reads: “Discover. Explore. Enjoy.”.
Title: 45 characters
Your title is a healthy 45 characters: “TAAG | Book Flight, Hotel and Online Check-in”.
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.
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://flytaag.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 (1,477 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages slow to respond
https://flytaag.com/en/Plan/Luggage/Excess-luggage and https://flytaag.com/en/Plan/Special-needs/Babies-and-children took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 83 found) and read each the way a search engine does.
7 checks passed
Linked pages load
12 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 12 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 12 pages that loaded have a <title>.
Best practices
23 small tap targets
23 of 44 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
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.
A 55-field form
Your longest form asks for 55 fields (0 required). Every extra field lowers completion.
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 350 words of copy
The homepage carries about 350 words of visible text.
3 checks passed
20 calls to action
The homepage has 20 calls to action, for example “Book Flight”, “Book now” and “Book your transfer”.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Direct contact links
Visitors can reach you directly: 4 phone links and 0 email links.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.
10 cookies set on arrival
10Opening the homepage sets 10 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.
16 other companies contacted
Loading the homepage contacts 16 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 flytaag.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
- Hosting
- Claranet
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 49 issues on flytaag.com, including 23 speed issues, 5 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.