Core Web Vitals for Persian sites: LCP, CLS, INP

Core Web Vitals for Persian sites means LCP, CLS, and INP on a real phone. Heavy images, too many font weights, and full-screen sliders are the usual cause. KGSM on kgsm.ir treats this in the design sprint, not as a last patch. Speed is part of SEO and must be in web design and, when needed, web programming from day one. Send the homepage URL via contact.

This guide — Core Web Vitals for Persian sites: LCP, CLS, INP — is written from KGSM delivery work: scoped first versions, staged releases, and support after handoff.

Audience, risk, and how KGSM works

A Persian-site owner whose mobile is slow or who sees poor LCP, CLS, and INP in Search or PageSpeed

Poor vitals mean phone users bounce, ads get expensive, and Google counts experience against you.

KGSM closes speed in design and technical SEO together: images, Persian fonts, scripts, and hosting — not a fake desktop score.

LCP: make the largest element light and early

LCP is usually the hero image, a slider, or a large heading waiting on a late font. Compress article covers as JPEG or WebP and set dimensions in HTML. Do not lazy-load the hero; lazy-load below the fold. Drop the full-screen slider or make slide one the same light hero file. On Iranian hosting keep the file path short; a foreign CDN can answer late from inside Iran. KGSM budgets hero kilobytes in web design instead of using an advertising-camera original. Preload only the body font weight. If LCP is text, load the font with font-display=swap so copy is not invisible. Do not celebrate a desktop PageSpeed score; the mobile field in Search Console is the Iranian user’s experience. A homepage under about two and a half seconds on 4G is a practical version-one target, not a lab one hundred.

Do not lazy-load the hero; set dimensions in HTML. A five-image slider pushed mobile LCP over four seconds until slide one became the hero.

CLS: stop RTL layout shift

On Persian sites CLS often comes from a top banner, a fallback font with different width, a slider, and a late ad. Reserve width and height for images so the paragraph does not jump after load. Plan space for eNamad, chat, and the cookie bar from the start. If Vazir or IRANSans arrives late and glyph width changes, the RTL menu jumps. Cut weights and keep font metrics close. KGSM drops auto sliders for CLS and distraction unless there is one message. A sticky mobile call bar that changes height without a reserve hurts the score. Late icon fonts cause the same jump; inline SVG is more stable. After a WordPress theme change, watch field CLS again because a new plugin will inject a bar. Test with network throttle, not office Wi-Fi.

Third-party chat wrecked menu INP; it moved to after click. Limit Persian fonts to two weights and use swap.

INP: a tap should answer in the same moment

INP is the delay after a click or tap. A heavy mobile menu, slider JavaScript, and several tag managers at once lock input. Cut third-party chat, maps, and duplicate analytics to after interaction or to one tool. Keep scroll handlers and animation light on the main thread. KGSM splits the front-end bundle in web programming so the first page loads only what is needed to see and to submit a form. Do not tie the buy or submit button to a heavy library. Test on a mid-range Iranian phone; a developer laptop lies. If a front-end framework hydrates the whole page, a corporate brochure may be better as server HTML and INP improves by itself.

Remove the full-screen slider from the homepage. Four font weights showed RTL menu CLS on every first visit.

Treat Persian fonts, images, and hosting as one job

Persian vitals do not recover if fonts and hosting stay wrong. Two font weights, subsetting if you have the tools, and no four families at once. Compress images before the panel upload; put editor training in the handoff or an eight-megabyte cover returns tomorrow. Measure hosting with TTFB on Iranian mobile. Turn on page cache and HTTP/2. After that, SEO watches Chrome field data because the lab is not the field. KGSM prices this pack inside design and development so speed is not «phase two». If a ready theme loads every plugin, put vitals cost in the redesign estimate. For an improvement plan, send a PageSpeed link and the host via contact so version one is based on real work, not a laptop score. Remove autoplay video from the mobile hero.

An eight-megabyte cover stopped after editor training and LCP recovered. Load chat and maps after user interaction.

Measure TTFB on Iranian mobile, not office Wi-Fi. A foreign CDN was slow from inside Iran; static files moved to a nearer host.

Desktop score was 95 and mobile field was red; the decision followed the field. Train editors so uncompressed covers are not uploaded.

Do not treat the lab score as Search Console field data. A five-image slider pushed mobile LCP over four seconds until slide one became the hero.

Third-party chat wrecked menu INP; it moved to after click. Check a new plugin for mobile CLS before you publish.

Implementation checklist

• Do not lazy-load the hero; set dimensions in HTML.
• Limit Persian fonts to two weights and use swap.
• Remove the full-screen slider from the homepage.
• Load chat and maps after user interaction.
• Measure TTFB on Iranian mobile, not office Wi-Fi.
• Train editors so uncompressed covers are not uploaded.
• Do not treat the lab score as Search Console field data.
• Check a new plugin for mobile CLS before you publish.

Field scenario 1

A five-image slider pushed mobile LCP over four seconds until slide one became the hero.

Do not lazy-load the hero; set dimensions in HTML.

Field scenario 2

Third-party chat wrecked menu INP; it moved to after click.

Limit Persian fonts to two weights and use swap.

Field scenario 3

Four font weights showed RTL menu CLS on every first visit.

Remove the full-screen slider from the homepage.

Field scenario 4

An eight-megabyte cover stopped after editor training and LCP recovered.

Load chat and maps after user interaction.

Field scenario 5

A foreign CDN was slow from inside Iran; static files moved to a nearer host.

Measure TTFB on Iranian mobile, not office Wi-Fi.

Field scenario 6

Desktop score was 95 and mobile field was red; the decision followed the field.

Train editors so uncompressed covers are not uploaded.

Related KGSM pages

Continue with KGSM services: سئو و بهینه‌سازی, طراحی سایت. Related reading: راهنمای سئو سایت فارسی ۱۴۰۵ — چک‌لیست عملی برای رتبه گوگل, شروع کار با Google Search Console برای سایت ایرانی. For a scoped estimate, use the contact form.

When you apply this on a live team, write it as an operating rule, not a slide: Do not lazy-load the hero; set dimensions in HTML. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Limit Persian fonts to two weights and use swap. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Remove the full-screen slider from the homepage. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Load chat and maps after user interaction. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Measure TTFB on Iranian mobile, not office Wi-Fi. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Train editors so uncompressed covers are not uploaded. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Do not treat the lab score as Search Console field data. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Check a new plugin for mobile CLS before you publish. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: A five-image slider pushed mobile LCP over four seconds until slide one became the hero. Then assign an owner and a review date so the rule survives the first busy week.