Website review, no card needed

syrian-airlines.net logo

syrian-airlines.net website review

Visit site (opens in a new tab)Reviewed 28 October 202635 issues · 66 checks

This review found 35 issues worth fixing on syrian-airlines.net, 13 of them high impact, across 66 checks. The most urgent: reduce unused JavaScript. 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
4.4 s2.0 sMay 9Oct 242.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.5 s
May 16, 20263.7 s
May 23, 20263.7 s
May 30, 20263.8 s
Jun 6, 20263.9 s
Jun 13, 20264.0 s
Jun 20, 20264.0 s
Jun 27, 20263.0 s
Jul 4, 20263.0 s
Jul 11, 20263.0 s
Jul 18, 20263.1 s
Jul 25, 20263.7 s
Aug 1, 20263.9 s
Aug 8, 20264.0 s
Aug 15, 20264.1 s
Aug 22, 20264.1 s
Aug 29, 20263.7 s
Sep 5, 20263.3 s
Sep 12, 20262.9 s
Sep 19, 20262.6 s
Sep 26, 20262.5 s
Oct 3, 20262.4 s
Oct 10, 20262.3 s
Oct 17, 20262.3 s
Oct 24, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
354 ms244 msMay 9Oct 24270 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026257 ms
May 16, 2026268 ms
May 23, 2026273 ms
May 30, 2026278 ms
Jun 6, 2026287 ms
Jun 13, 2026289 ms
Jun 20, 2026289 ms
Jun 27, 2026279 ms
Jul 4, 2026288 ms
Jul 11, 2026297 ms
Jul 18, 2026303 ms
Jul 25, 2026341 ms
Aug 1, 2026307 ms
Aug 8, 2026289 ms
Aug 15, 2026282 ms
Aug 22, 2026286 ms
Aug 29, 2026278 ms
Sep 5, 2026270 ms
Sep 12, 2026264 ms
Sep 19, 2026261 ms
Sep 26, 2026260 ms
Oct 3, 2026259 ms
Oct 10, 2026261 ms
Oct 17, 2026262 ms
Oct 24, 2026270 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 syrian-airlines.net (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. syrian-airlines.net at 0.8 s0.8 s
  2. syrian-airlines.net at 1.6 s1.6 s
  3. syrian-airlines.net at 2.4 s2.4 s
  4. syrian-airlines.net at 3.2 s3.2 s
  5. syrian-airlines.net at 4.0 s4.0 s
  6. syrian-airlines.net at 4.8 s4.8 s
  7. syrian-airlines.net at 5.6 s5.6 s
  8. syrian-airlines.net at 6.4 s6.4 s

Speed

9 to fix47
  • Reduce unused JavaScript

    2.4 s · 402 KiB

    About 402 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.

  • Mobile performance score: 47

    47/100

    Your mobile performance score is 47 (desktop: 88). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Use efficient cache lifetimes

    900 ms · 860 KiB

    9 files are served with short cache lifetimes, so returning visitors download them again (860 KiB).

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, Google/Doubleclick Ads and syrlines.com and others), adding 1.9 MB and 695 ms of main-thread time.

  • Google Tag Manager adds 691 ms

    691 ms

    Google Tag Manager costs a phone 691 ms of main-thread work and 694 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.

  • Improve image delivery

    715 KiB

    9 images could be 715 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Render-blocking requests

    300 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 300 ms.

  • Main-thread work: 2.9 s

    A phone's processor spends 2.9 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • syrlines.com adds 2 ms

    2 ms

    syrlines.com costs a phone 2 ms of main-thread work and 1.2 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.

  • 11 long tasks on the main thread

    11 long tasks block the main thread while loading, the longest for 168 ms. During a long task the page ignores taps.

  • Reduce unused CSS

    150 ms · 13 KiB

    About 13 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.

  • Phones get a much slower page than desktops

    Desktop scores 88 but mobile only 47. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • 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.

Core Web Vitals

8 to fix67
  • 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: 12.3 s

    12.3 s

    Your largest element takes 12.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Syria’s Gateway to the World Book your SYRIAN flight in a f…”.

  • First Contentful Paint: 5.3 s

    5.3 s

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

  • Time to Interactive: 12.6 s

    12.6 s

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

  • Speed Index: 7.8 s

    7.8 s

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

  • Real-user INP: 279 ms

    279 ms

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

  • Total Blocking Time: 431 ms

    431 ms

    Scripts block taps and scrolling for 431 ms in total while the page loads. Good is under 200 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) held steady for real visitors

    +1%

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

6 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Real-user TTFB: 479 ms

    479 ms

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

  • Largest content (LCP) got 36% faster for real visitors

    -36%

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

  • Cumulative Layout Shift: 0.042

    0.042

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

Images and page weight

4 to fix58
  • Page weight: 2.5 MB in 53 requests

    2.5 MB

    Your homepage downloads 2.5 MB in 53 requests on a phone: images 1.5 MB (15), scripts 932 KiB (18) and fonts 49 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 8 images in older formats

    8 images (1.0 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.

  • 9 images below the first screen load straight away

    9 images further down the page (1.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 5 images far larger than shown

    450 KiB

    5 images are downloaded at several times the size a phone draws them, for example 01M32BK6KW0XHX8DWD4KEMCF9E.jpg at 1,638 px wide, shown at 292 px. Resized copies would save about 450 KiB.

  • About 0.7 g of CO₂ per visit

    0.71 g

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

Accessibility

3 to fixGoogle 9094
  • 3 buttons without a name

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

  • 2 text elements with low contrast

    2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

1 checks passed
  • 42 automated accessibility rules passed

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

SEO

5 to fixGoogle 10076
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

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

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

4 checks passed
  • Meta description: 119 characters

    Your meta description is 119 characters: “احجز رحلاتك مع السورية - شركة الطيران الوطنية للسفر المريح والآمن. ابحث عن الرحلات، قارن الأسعار، واحجز رحلتك المثالية.”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “السورية - نظام حجز الرحلات | SYRIAN - Flight Booking System”.

  • 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

2 to fix63
  • Most text only appears after JavaScript runs

    0%

    A phone browser shows 1,079 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

  • 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://syrian-airlines.net/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
  • 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.

Best practices

Google 96100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix50
  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • 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 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 1,079 words of copy

    The homepage carries about 1,079 words of visible text.

2 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact Us” and “Book”.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before 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.

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 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.

  • 8 other companies contacted

    Loading the homepage contacts 8 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 syrian-airlines.net, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Analytics
Google Analytics
Hosting
netcup GmbH

Company

Founded
1961
Headquarters
Damascus

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on syrian-airlines.net, including 17 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

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