Programmable

Website review, no card needed

moghim24.net logo

moghim24.net website review

Visit site (opens in a new tab)Reviewed 8 November 202623 issues · 78 checks

This review found 23 issues worth fixing on moghim24.net, 6 of them high impact, across 78 checks. The most urgent: render-blocking requests. 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

Site score

79C

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
12.6 s4.5 sAug 22Oct 315.4 s
Show as table
DateReal-visitor load time (LCP)
Aug 22, 202611.7 s
Aug 29, 202611.5 s
Sep 5, 202610.9 s
Sep 12, 202610.3 s
Sep 19, 20269.6 s
Sep 26, 20269.8 s
Oct 3, 202610.0 s
Oct 10, 202610.0 s
Oct 17, 20268.8 s
Oct 24, 20267.3 s
Oct 31, 20265.4 s
Real-visitor tap response (INP)75th percentile, phones
453 ms295 msAug 22Oct 31435 ms
Show as table
DateReal-visitor tap response (INP)
Aug 22, 2026395 ms
Aug 29, 2026350 ms
Sep 5, 2026313 ms
Sep 12, 2026355 ms
Sep 19, 2026350 ms
Sep 26, 2026362 ms
Oct 3, 2026379 ms
Oct 10, 2026378 ms
Oct 17, 2026405 ms
Oct 24, 2026425 ms
Oct 31, 2026435 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

moghim24.ir (opens in a new tab)
Full-page screenshot of moghim24.net (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. moghim24.net at 1.5 s1.5 s
  2. moghim24.net at 3.0 s3.0 s
  3. moghim24.net at 4.6 s4.6 s
  4. moghim24.net at 6.1 s6.1 s
  5. moghim24.net at 7.6 s7.6 s
  6. moghim24.net at 9.1 s9.1 s
  7. moghim24.net at 10.6 s10.6 s
  8. moghim24.net at 12.2 s12.2 s

Speed

4 to fix85

  • Render-blocking requests

    2.0 s

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

  • Main-thread work: 4.2 s

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

  • Mobile performance score: 85

    85/100

    Your mobile performance score is 85. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    264 KiB

    About 264 KiB of JavaScript is downloaded but never used on this page.

  • Reduce unused CSS

    130 ms · 34 KiB

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

  • 7 long tasks on the main thread

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google Tag Manager, Google Analytics and moghim24.services), adding 179 KiB and 112 ms of main-thread time.

  • Improve image delivery

    36 KiB

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

  • Use efficient cache lifetimes

    16 KiB

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

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

1 checks passed

  • Server response: 347 ms

    347 ms

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

Core Web Vitals

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

  • Speed Index: 8.1 s

    8.1 s

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

  • Real-user LCP: 3.7 s

    3.7 s

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

  • Real-user INP: 388 ms

    388 ms

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

  • Real-user FCP: 2.2 s

    2.2 s

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • Time to Interactive: 7.2 s

    7.2 s

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

  • Total Blocking Time: 303 ms

    303 ms

    Scripts block taps and scrolling for 303 ms in total while the page loads. Good is under 200 ms.

  • Tap response (INP) got 15% slower for real visitors

    +15%

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

5 checks passed

  • Real-user CLS: 0.06

    0.06

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

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

    -45%

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

  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.027

    0.027

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

  • Largest Contentful Paint: 1.4 s

    1.4 s

    Your largest element renders in 1.4 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “سفر بعدی‌ات از همین‌جا شروع می‌شود”.

Images and page weight

100

  • About 0.3 g of CO₂ per visit

    0.29 g

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

4 checks passed

  • Page weight: 1.0 MB in 36 requests

    1.0 MB

    Your homepage downloads 1.0 MB in 36 requests on a phone: scripts 763 KiB (13), fonts 103 KiB (3) and HTML 88 KiB (1). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

3 to fixGoogle 10096

  • Scrollable region must have keyboard access (2 elements)

    Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

2 checks passed

  • Every image has alt text

    All 28 images in the HTML carry an alt attribute.

  • 53 automated accessibility rules passed

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

SEO

Google 92100

  • 25 internal links, 4 external

    The homepage links to 25 pages on moghim24.net and 4 external pages.

8 checks passed

  • Meta description: 130 characters

    Your meta description is 130 characters: “مقایسه قیمت و رزرو آنلاین بلیط هواپیما داخلی و خارجی، هتل و تور از آژانس‌های دارای مجوز در یک جستجو، با پشتیبانی ۲۴ ساع…”.

  • One H1 headline

    Your main headline reads: “سفر بعدی‌ات از همین‌جا شروع می‌شود”.

  • Title: 47 characters

    Your title is a healthy 47 characters: “مقیم ۲۴ | مقایسه و رزرو بلیط هواپیما، هتل و تور”.

  • Canonical URL set

    The canonical URL is https://moghim24.ir/.

  • Structured data in place

    Structured data found: TravelAgency and WebSite.

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

  • XML sitemap found

    Your XML sitemap is reachable at https://moghim24.ir/sitemap.xml.

AI search readiness

100

  • No llms.txt

    There is no https://moghim24.ir/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.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

Other pages

3 to fix86

  • 4 pages share 2 titles

    https://moghim24.ir/home and / all use the title “مقیم ۲۴ | مقایسه و رزرو بلیط هواپیما، هتل و تور”, 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://moghim24.ir/flight and https://moghim24.ir/flight/THR-KIH use the same meta description. A description written for each page earns more clicks.

  • 11 links to non-canonical URLs

    Your homepage links to 11 pages by a URL that isn't their canonical one, for example https://moghim24.ir/flight/THR-MHD, whose canonical is https://moghim24.ir/flight/tehran-mashhad. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 pages with very little text

    /, https://moghim24.ir/flight, https://moghim24.ir/hotel, https://moghim24.ir/tour, https://moghim24.ir/flight/THR-MHD and https://moghim24.ir/flight/THR-KIH and 9 others 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.

  • 9 pages slow to respond

    /, https://moghim24.ir/flight, https://moghim24.ir/hotel, https://moghim24.ir/tour, https://moghim24.ir/flight/THR-MHD and https://moghim24.ir/flight/THR-KIH and 3 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 17 found) and read each the way a search engine does.

5 checks passed

  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “TypeError: Cannot read properties of undefined (reading 'getRegistrations')”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix78

  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • Only about 40 words

    The homepage has only about 40 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

6 checks passed

  • 1 call to action

    The homepage has 1 call to action, for example “call تماس با پشتیبانی”.

  • 1 short form

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

  • Social proof on the page

    Social proof on the homepage: 12 customer or partner logos and 1 trust badge.

  • Direct contact links

    Visitors can reach you directly: 7 phone links and 2 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix

  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads 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.

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

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 moghim24.net, 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
Hosting
Dade Samane Fanava Company (PJS)

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 23 issues on moghim24.net, including 12 speed 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