Website review, no card needed

irantalent.com logo

irantalent.com website review

Visit site (opens in a new tab)Reviewed 3 November 202637 issues · 83 checks

This review found 37 issues worth fixing on irantalent.com, 10 of them high impact, across 83 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.8 s4.0 sMay 16Oct 314.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20264.1 s
May 23, 20264.3 s
May 30, 20264.5 s
Jun 6, 20264.7 s
Jun 13, 20264.7 s
Jun 20, 20264.5 s
Jun 27, 20264.4 s
Jul 4, 20264.2 s
Jul 11, 20264.2 s
Jul 18, 20264.1 s
Jul 25, 20264.1 s
Aug 1, 20264.1 s
Aug 8, 20264.1 s
Aug 15, 20264.1 s
Aug 22, 20264.2 s
Aug 29, 20264.1 s
Sep 5, 20264.1 s
Sep 12, 20264.1 s
Sep 19, 20264.1 s
Sep 26, 20264.2 s
Oct 3, 20264.2 s
Oct 10, 20264.2 s
Oct 17, 20264.2 s
Oct 24, 20264.1 s
Oct 31, 20264.1 s
Real-visitor tap response (INP)75th percentile, phones
291 ms228 msMay 16Oct 31278 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026241 ms
May 23, 2026235 ms
May 30, 2026240 ms
Jun 6, 2026250 ms
Jun 13, 2026261 ms
Jun 20, 2026277 ms
Jun 27, 2026283 ms
Jul 4, 2026284 ms
Jul 11, 2026280 ms
Jul 18, 2026271 ms
Jul 25, 2026271 ms
Aug 1, 2026274 ms
Aug 8, 2026275 ms
Aug 15, 2026281 ms
Aug 22, 2026282 ms
Aug 29, 2026282 ms
Sep 5, 2026284 ms
Sep 12, 2026281 ms
Sep 19, 2026283 ms
Sep 26, 2026284 ms
Oct 3, 2026282 ms
Oct 10, 2026281 ms
Oct 17, 2026280 ms
Oct 24, 2026279 ms
Oct 31, 2026278 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 irantalent.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. irantalent.com at 1.5 s1.5 s
  2. irantalent.com at 3.0 s3.0 s
  3. irantalent.com at 4.5 s4.5 s
  4. irantalent.com at 6.0 s6.0 s
  5. irantalent.com at 7.5 s7.5 s
  6. irantalent.com at 9.0 s9.0 s
  7. irantalent.com at 10.5 s10.5 s
  8. irantalent.com at 12.0 s12.0 s

Speed

11 to fix65
  • Reduce unused JavaScript

    1.1 s · 715 KiB

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

  • Mobile performance score: 65

    65/100

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

  • Font display

    650 ms

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

  • Use efficient cache lifetimes

    523 KiB

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

  • Render-blocking requests

    450 ms

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

  • Google Tag Manager adds 383 ms

    383 ms

    Google Tag Manager costs a phone 383 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.

  • Reduce unused CSS

    310 ms · 58 KiB

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

  • Improve image delivery

    327 KiB

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

  • Main-thread work: 3.0 s

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

  • 13 long tasks on the main thread

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

  • irtalent.cloud adds 0 ms

    0 ms

    irtalent.cloud costs a phone 0 ms of main-thread work and 346 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.

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, Clarity and Other Google APIs/SDKs and others), adding 991 KiB and 470 ms of main-thread time.

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

1 checks passed
  • Server response: 165 ms

    165 ms

    Your server sent the HTML in 165 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 CLS: 0.92

    0.92

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

  • Time to Interactive: 16.5 s

    16.5 s

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

  • Largest Contentful Paint: 4.4 s

    4.4 s

    Your largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Find your dream job Hire the best candidate Register for jo…”. Most of its time is resource load delay (2.2 s).

  • Speed Index: 6.3 s

    6.3 s

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

  • Real-user INP: 403 ms

    403 ms

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

  • Real-user FCP: 2.1 s

    2.1 s

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

  • Real-user TTFB: 1.4 s

    1.4 s

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

  • Total Blocking Time: 572 ms

    572 ms

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

  • 4 images without width and height

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

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

    +17%

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

  • Largest content (LCP) held steady for real visitors

    -1%

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

3 checks passed
  • Real-user LCP: 2.5 s

    2.5 s

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

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

    0.002

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

Images and page weight

2 to fix75
  • Page weight: 2.8 MB in 128 requests

    2.8 MB

    Your homepage downloads 2.8 MB in 128 requests on a phone: scripts 1.9 MB (68), images 404 KiB (35) and fonts 269 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • 3 images far larger than shown

    256 KiB

    3 images are downloaded at several times the size a phone draws them, for example employer_logo_8135_200117.jpeg at 1,241 px wide, shown at 40 px. Resized copies would save about 256 KiB.

  • 3 images in older formats

    3 images (258 KiB) 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.

  • About 0.8 g of CO₂ per visit

    0.78 g

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

1 checks passed
  • Images load when needed

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

Accessibility

6 to fixGoogle 8791
  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • 10 text elements with low contrast

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

  • 2 tap targets too small

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

2 checks passed
  • Every image has alt text

    All 46 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

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

SEO

3 to fixGoogle 10086
  • 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 favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 109 internal links, 18 external

    The homepage links to 109 pages on irantalent.com and 18 external pages.

6 checks passed
  • Meta description: 150 characters

    Your meta description is 150 characters: “IranTalent is the leading job site for professionals. Find the best jobs & career opportunities and send your CV to Int…”.

  • Title: 47 characters

    Your title is a healthy 47 characters: “IranTalent Recruitment & Jobs for Professionals”.

  • Canonical URL set

    The canonical URL is https://www.irantalent.com/.

  • Structured data in place

    Structured data found: FAQPage.

  • 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://www.irantalent.com/sitemap.xml.

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.irantalent.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 (795 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 1 page without an H1

    https://www.irantalent.com/en/companies has no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages with very little text

    https://www.irantalent.com/cv, https://www.irantalent.com/reports, https://www.irantalent.com/blog, https://www.irantalent.com/tests and https://www.irantalent.com/farsi 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.

  • 3 pages slow to respond

    https://www.irantalent.com/en/companies, https://www.irantalent.com/reports and https://www.irantalent.com/en/company/taxi-maxim/faa00b2d-29c2-46ad-9d9a-15cff9324abf/job-positions took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

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

Best practices

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://accounts.google.com/gsi/style' from origin 'https://www.irantalent.com' has been b…”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix90
  • 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 399 words of copy

    The homepage carries about 399 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Register for jobs” and “Company Register”.

  • 19 calls to action

    The homepage has 19 calls to action, for example “Register for jobs”, “Company Register” and “Apply”.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

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.

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

  • 6 other companies contacted

    Loading the homepage contacts 6 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 irantalent.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
Analytics
Google Tag Manager | Microsoft Clarity
Hosting
Noyan Abr Arvan Co. ( Private Joint Stock)

Hiring

Hiring
19 open roles
Job board
careers page

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on irantalent.com, including 21 speed issues, 3 SEO issues and 1 conversion gap. 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