Website review, no card needed

akbartravels.com logo

akbartravels.com website review

Visit site (opens in a new tab)Reviewed 18 October 202643 issues · 87 checks

This review found 43 issues worth fixing on akbartravels.com, 21 of them high impact, across 87 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
7.5 s4.3 sApr 25Oct 105.9 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20265.7 s
May 2, 20265.7 s
May 9, 20265.7 s
May 16, 20266.0 s
May 23, 20265.7 s
May 30, 20265.8 s
Jun 6, 20265.6 s
Jun 13, 20266.2 s
Jun 20, 20266.2 s
Jun 27, 20266.6 s
Jul 4, 20267.1 s
Jul 11, 20265.9 s
Jul 18, 20265.9 s
Jul 25, 20265.6 s
Aug 1, 20265.5 s
Aug 8, 20265.8 s
Aug 15, 20265.8 s
Aug 22, 20265.6 s
Aug 29, 20264.6 s
Sep 5, 20264.6 s
Sep 12, 20265.3 s
Sep 19, 20265.5 s
Sep 26, 20265.3 s
Oct 3, 20265.5 s
Oct 10, 20265.9 s
Real-visitor tap response (INP)75th percentile, phones
172 ms107 msApr 25Oct 10133 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026158 ms
May 2, 2026150 ms
May 9, 2026147 ms
May 16, 2026150 ms
May 23, 2026140 ms
May 30, 2026152 ms
Jun 6, 2026157 ms
Jun 13, 2026157 ms
Jun 20, 2026161 ms
Jun 27, 2026151 ms
Jul 4, 2026139 ms
Jul 11, 2026127 ms
Jul 18, 2026114 ms
Jul 25, 2026139 ms
Aug 1, 2026139 ms
Aug 8, 2026142 ms
Aug 15, 2026164 ms
Aug 22, 2026142 ms
Aug 29, 2026154 ms
Sep 5, 2026158 ms
Sep 12, 2026147 ms
Sep 19, 2026138 ms
Sep 26, 2026133 ms
Oct 3, 2026126 ms
Oct 10, 2026133 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

Full-page screenshot of akbartravels.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. akbartravels.com at 0.4 s0.4 s
  2. akbartravels.com at 0.8 s0.8 s
  3. akbartravels.com at 1.1 s1.1 s
  4. akbartravels.com at 1.5 s1.5 s
  5. akbartravels.com at 1.9 s1.9 s
  6. akbartravels.com at 2.3 s2.3 s
  7. akbartravels.com at 2.6 s2.6 s
  8. akbartravels.com at 3.0 s3.0 s

Speed

6 to fix63
  • Use efficient cache lifetimes

    14.3 s · 3.3 MB

    28 files are served with short cache lifetimes, so returning visitors download them again (3.3 MB).

  • Improve image delivery

    13.7 s · 3.1 MB

    10 images could be 3.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 13.7 s faster on a phone.

  • Render-blocking requests

    2.8 s

    12 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.8 s.

  • Mobile performance score: 63

    63/100

    Your mobile performance score is 63 (desktop: 54). Pages that score under 90 lose visitors before the first paint.

  • Duplicated JavaScript

    350 ms · 43 KiB

    43 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 350 ms faster on a phone.

  • Reduce unused CSS

    300 ms · 53 KiB

    About 53 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • 6 third-party services on the page

    6 third-party services load with your homepage (jQuery CDN, JSDelivr CDN and Unpkg and others), adding 398 KiB and 138 ms of main-thread time.

  • Reduce unused JavaScript

    150 ms · 21 KiB

    About 21 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Legacy JavaScript

    150 ms · 9 KiB

    Polyfills for old browsers add 9 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 75 ms. During a long task the page ignores taps.

  • Document request latency

    44 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Minify CSS

    13 KiB

    13 KiB could be saved by minifying CSS.

  • Minify JavaScript

    7 KiB

    7 KiB could be saved by minifying JavaScript.

  • 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: 0.7 s

    A phone's processor spends 0.7 s on main-thread work while loading, 176 ms of it running JavaScript. That is comfortably low.

  • Server response: 25 ms

    25 ms

    Your server sent the HTML in 25 ms, well inside Google's 600 ms guideline.

Core Web Vitals

10 to fix33
  • 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: 6.4 s

    6.4 s

    Real visitors wait 6.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user CLS: 1.00

    1.00

    For real visitors the layout shifts by 1.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 5.4 s

    5.4 s

    Real visitors see the first content after 5.4 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 4.0 s

    4.0 s

    Real visitors wait 4.0 s for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest Contentful Paint: 21.7 s

    21.7 s

    Your largest element takes 21.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Chania”.

  • Time to Interactive: 21.9 s

    21.9 s

    The page becomes fully interactive after 21.9 s. Good is under 3.8 s.

  • First Contentful Paint: 3.8 s

    3.8 s

    The first text or image appears after 3.8 s on a phone. Good is under 1.8 s.

  • Speed Index: 5.7 s

    5.7 s

    Visually, the page fills in at 5.7 s (Speed Index). Good is under 3.4 s.

  • 6 images without width and height

    6 images have no width and height attributes, so the layout jumps as each one loads.

  • Largest content (LCP) held steady for real visitors

    0%

    Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 5.7 s to 5.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

4 checks passed
  • Real-user INP: 140 ms

    140 ms

    Real visitors wait 140 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Tap response (INP) got 16% faster for real visitors

    -16%

    Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 158 ms to 133 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Total Blocking Time: 25 ms

    25 ms

    Scripts block the page for only 25 ms while loading. Good is under 200 ms.

Images and page weight

5 to fix43
  • 2 images over 500 KB

    2 images weigh 2.7 MB together. On a phone connection a single image that size takes seconds.

  • Page weight: 3.8 MB in 50 requests

    3.8 MB

    Your homepage downloads 3.8 MB in 50 requests on a phone: images 3.3 MB (21), scripts 239 KiB (11) and fonts 148 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 9 images in older formats

    9 images (3.2 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.

  • 2 images far larger than shown

    458 KiB

    2 images are downloaded at several times the size a phone draws them, for example slider-1.png at 1,280 px wide, shown at 390 px. Resized copies would save about 458 KiB.

  • 8 images below the first screen load straight away

    8 images further down the page (499 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.1 g of CO₂ per visit

    1.07 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.07 g of CO₂e: 129.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

9 to fixGoogle 6785
  • 15 buttons without a name

    15 buttons have no accessible name, so screen readers announce just “button”.

  • Invalid ARIA attributes

    2 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • Orphan list items

    Some list items are not inside a list.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Positive tabindex

    2 elements have a tabindex above 0, which scrambles the keyboard order.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • All page content should be contained by landmarks (12 elements)

    All page content should be contained by landmarks: 12 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.

  • 6 form fields without a label

    6 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

    Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 23 images in the HTML carry an alt attribute.

  • 40 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 10 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

8 to fixGoogle 9159
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (20 characters)

    Your title is only 20 characters: “AkbarOffshore - Home”. 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.

  • 3 H1 headlines

    There are 3 <h1> headlines (“TOP COUNTRIES TO TRAVEL”, “AFFORDABLE TRAVEL DEALS FROM” and “NEWS AND STORIES TRAVELS”). One clear main headline is easier for people and search engines.

  • 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://www.akbartravels.us/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at akbartravels.us/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.

  • 7 internal links, 13 external

    The homepage links to 7 pages on akbartravels.com and 13 external pages.

AI search readiness

1 to fix88
  • 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://www.akbartravels.us/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 (245 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 1 page without a meta description

    https://www.akbartravels.us/hotels has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.akbartravels.us/hotels has no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 internal pages checked

    We fetched 4 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 4 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 4 pages that loaded have a <title>.

Best practices

Google 100100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    8 of 9 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix60
  • 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.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • 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 302 words of copy

    The homepage carries about 302 words of visible text.

3 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Contact Us”.

  • 1 short form

    A short form (4 fields at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

  • 7 other companies contacted

    Loading the homepage contacts 7 hosts 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 akbartravels.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
Angular

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on akbartravels.com, including 16 speed issues, 8 SEO issues and 2 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25