Website review, no card needed

mohaymen.ir logo

mohaymen.ir website review

Visit site (opens in a new tab)Reviewed 19 November 202637 issues · 77 checks

This review found 37 issues worth fixing on mohaymen.ir, 17 of them high impact, across 77 checks. The most urgent: improve image delivery. 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.8 s5.4 sMay 30Nov 146.5 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20265.9 s
Jun 6, 20266.1 s
Jun 13, 20266.1 s
Jun 20, 20266.3 s
Jun 27, 20266.2 s
Jul 4, 20266.2 s
Jul 11, 20266.0 s
Jul 18, 20265.9 s
Jul 25, 20266.0 s
Aug 1, 20266.2 s
Aug 8, 20266.5 s
Aug 15, 20266.8 s
Aug 22, 20267.2 s
Aug 29, 20267.4 s
Sep 5, 20267.3 s
Sep 12, 20267.5 s
Sep 19, 20267.4 s
Sep 26, 20267.2 s
Oct 3, 20267.0 s
Oct 10, 20266.1 s
Oct 17, 20265.7 s
Oct 24, 20265.9 s
Oct 31, 20266.1 s
Nov 7, 20266.3 s
Nov 14, 20266.5 s
Real-visitor tap response (INP)75th percentile, phones
120 ms92 msMay 30Nov 14106 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202695 ms
Jun 6, 202698 ms
Jun 13, 2026109 ms
Jun 20, 2026107 ms
Jun 27, 2026111 ms
Jul 4, 2026111 ms
Jul 11, 2026102 ms
Jul 18, 2026107 ms
Jul 25, 2026110 ms
Aug 1, 2026110 ms
Aug 8, 2026108 ms
Aug 15, 2026111 ms
Aug 22, 2026110 ms
Aug 29, 2026109 ms
Sep 5, 2026115 ms
Sep 12, 2026116 ms
Sep 19, 2026117 ms
Sep 26, 2026112 ms
Oct 3, 2026111 ms
Oct 10, 2026113 ms
Oct 17, 2026113 ms
Oct 24, 2026113 ms
Oct 31, 2026113 ms
Nov 7, 2026107 ms
Nov 14, 2026106 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 mohaymen.ir (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mohaymen.ir at 1.2 s1.2 s
  2. mohaymen.ir at 2.3 s2.3 s
  3. mohaymen.ir at 3.5 s3.5 s
  4. mohaymen.ir at 4.7 s4.7 s
  5. mohaymen.ir at 5.8 s5.8 s
  6. mohaymen.ir at 7.0 s7.0 s
  7. mohaymen.ir at 8.2 s8.2 s
  8. mohaymen.ir at 9.3 s9.3 s

Speed

4 to fix66
  • Improve image delivery

    1.1 s · 1.1 MB

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

  • Reduce unused CSS

    1.4 s · 334 KiB

    About 334 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.4 s faster on a phone.

  • Mobile performance score: 66

    66/100

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

  • Font display

    950 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 950 ms).

  • Reduce unused JavaScript

    150 ms · 65 KiB

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

  • Minify JavaScript

    150 ms · 16 KiB

    16 KiB could be saved by minifying JavaScript.

  • 3 third-party services on the page

    3 third-party services load with your homepage (jQuery CDN, Cloudflare CDN and Google Fonts), adding 120 KiB and 45 ms of main-thread time.

  • Minify CSS

    7 KiB

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

2 checks passed
  • Main-thread work: 1.2 s

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

  • Server response: 466 ms

    466 ms

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

Core Web Vitals

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

  • Real-user LCP: 8.2 s

    8.2 s

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

  • Real-user FCP: 5.8 s

    5.8 s

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

  • Real-user TTFB: 7.1 s

    7.1 s

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

  • Speed Index: 14.1 s

    14.1 s

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

  • Largest Contentful Paint: 8.3 s

    8.3 s

    Your largest element takes 8.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below. Most of its time is resource load delay (7.0 s).

  • Time to Interactive: 8.3 s

    8.3 s

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

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

    +10%

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

  • Largest content (LCP) held steady for real visitors

    +7%

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

5 checks passed
  • Real-user INP: 114 ms

    114 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Cumulative Layout Shift: 0.01

    0.01

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

  • First Contentful Paint: 1.1 s

    1.1 s

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

1 to fix85
  • Page weight: 2.9 MB in 133 requests

    2.9 MB

    Your homepage downloads 2.9 MB in 133 requests on a phone: images 1.9 MB (25), stylesheets 400 KiB (48) and scripts 392 KiB (54). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (341 KiB) is 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.

  • About 0.8 g of CO₂ per visit

    0.82 g

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

2 checks passed
  • 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

7 to fixGoogle 8788
  • 17 tap targets too small

    17 tap targets are too small or too close together to hit reliably with a finger.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • [role="img"] and [role="image"] elements must have alternative text (1 element)

    [role="img"] and [role="image"] elements must have alternative text: 1 element on the page fails this check, rated serious by axe-core.

  • 15 images without alt text

    15 images have no alt text, which hurts accessibility and image search.

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

    All page content should be contained by landmarks: 7 elements on the page fail this check, rated moderate by axe-core.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 12 links without text

    12 visible links have no text or label, so screen readers cannot say where they go.

  • Headings skip levels

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

1 checks passed
  • 39 automated accessibility rules passed

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

SEO

4 to fixGoogle 8381
  • No H1 headline

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No robots.txt

    There is no robots.txt at mohaymen.ir/robots.txt, the first file search crawlers ask for.

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

  • 121 internal links, 12 external

    The homepage links to 121 pages on mohaymen.ir and 12 external pages.

5 checks passed
  • Meta description: 155 characters

    Your meta description is 155 characters: “امروز از محصولات مهیمن به عنوان ابزارهایی قدرتمند برای حل مسائل و چالش‌های سازمان‌های بزرگ کشور در حوزه‌های مختلف فناور…”.

  • Title: 49 characters

    Your title is a healthy 49 characters: “شرکت مهیمن - گروه فناوری اطلاعات و ارتباطات مهیمن”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Article, ImageObject, Organization, Person and WebPage.

  • XML sitemap found

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

AI search readiness

1 to fix69
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing url, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

Other pages

5 to fix76
  • 2 pages share a title

    https://mohaymen.ir/values and https://mohaymen.ir/human-resources all use the title “Human Resources - گروه فناوری اطلاعات و ارتباطات مهیمن”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://mohaymen.ir/ar has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://mohaymen.ir/values and https://mohaymen.ir/human-resources use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://mohaymen.ir/human-resources, whose canonical is https://mohaymen.ir/values. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 10 pages without an H1

    https://mohaymen.ir/ar, https://mohaymen.ir/business-digitalization, https://mohaymen.ir/security, https://mohaymen.ir/data-center, https://mohaymen.ir/telecom and https://mohaymen.ir/banking and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 13 pages with very little text

    https://mohaymen.ir/ar, https://mohaymen.ir/business-digitalization, https://mohaymen.ir/security, https://mohaymen.ir/data-center, https://mohaymen.ir/telecom and https://mohaymen.ir/banking and 7 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.

  • 1 page slow to respond

    https://mohaymen.ir/human-resources took over 3 s to send its HTML from our server.

  • 14 internal pages checked

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

3 checks passed
  • Linked pages load

    13 pages of 14 loaded without an error (the rest turned automated requests away).

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7389
  • 19 small tap targets

    19 of 22 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • No HTML doctype

    The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Mixed content”).

2 checks passed
  • No console errors

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix36
  • 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 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 analytics detected

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

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

  • Only about 6 words

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

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

1 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage.

Privacy and tracking

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

  • 4 other companies contacted

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on mohaymen.ir, including 11 speed issues, 4 SEO issues and 6 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