Skip to main content
← Back to blog

SEO Umhlahlo Isinyathelo 5: UX / Umphakathi Wabasebenzisi — Indlela Abavakashi Abazithola Ngayo I-Site Yakho Ethinta Uhlelo Lokubeka

·14 min read·by LANGR SEO

SEO Umhlahlo Isinyathelo 5: UX / Umphakathi Wabasebenzisi

Lena Isinyathelo 5 se-13-Step SEO Guide. Umphakathi wabasebenzisi manje usuyifakazela ukuthi uhlelo lokubeka — i-Google ikala indlela abavakashi abahlangana ngayo ne-site yakho bese iphinda ibize ama-site abanikeza imiphumela esheshayo, efinyeleleka, nehlelekile.


Uhlelo lokuqukethwe (Isinyathelo 3) luthola lokho okushicilelwayo. Ukwakha izixhumanisi (Isinyathelo 4) kufakazela umbiko wakho. Nokho uma abavakashi befika kukhasi lakho bese beshayela bese behamba masinyane ngoba lingenamandla, liphukile kumafoni, noma alufinyeleleki — lokho akubalulekile. I-Google ilandelela lezi zimpawu futhi izisebenzisa ukumisa uhlelo lokubeka.

Kusukela ngo-2021, ukuvuselelwa kwe-Google's Page Experience kwenze i-UX yaba yisici esiqinile sokubeka. Ngo-2024, i-INP (Interaction to Next Paint) ithathe indawo ye-FID njengeCore Web Vital. Ngo-2026, lezi zimpawu ziba nesibopho esikhulu njengoba i-Google igxila kakhulu ezibalweni zokwaneliseka komsebenzisi ngaphezu kwezimpawu zendabuko.

Yini i-UX ye-SEO Ehlanganisa

Ukuthuthukiswa kwe-UX kwe-SEO kubandakanya izindawo eziyi-6:

  1. Core Web Vitals — Izilinganiso ze-UX ezisemthethweni ze-Google (LCP, INP, CLS)
  2. Ukuthuthukiswa kwe-Mobile — Umklamo ophendulayo, izinjongo zokuthinta, indawo yokubuka
  3. Ukufinyeleleka (WCAG) — Ukwenza ukuthi i-site yakho ifinyeleleke kubo bonke
  4. Izimpawu Zokuhlangenwe Nakho Kwekhasi — HTTPS, akukho zinyathelo ezithakazelisayo, ukuhamba okuphephile
  5. Izithakazelo Zokuhamba — Uhlaka lwe-site olusiza abasebenzisi nabahloli
  6. Ukuthuthukiswa Kwe-Above-the-Fold — Lokho abasebenzisi abakubona ngaphandle kokushelelela

1. Core Web Vitals (CWV)

I-Core Web Vitals yizilinganiso ezintathu ze-UX ezilinganiswayo ze-Google. Zilandelelwa ku-Chrome User Experience Report (CrUX) idatha futhi zithinta ngqo izinkomba.

Izilinganiso ezintathu:

MetricMeasuresGoodNeeds ImprovementPoor
LCP (Largest Contentful Paint)Ukusheshisa kokulayisha< 2.5s2.5s - 4.0s> 4.0s
INP (Interaction to Next Paint)Ukuphendula< 200ms200ms - 500ms> 500ms
CLS (Cumulative Layout Shift)Ukuzinza kokubona< 0.10.1 - 0.25> 0.25

LCP — Largest Contentful Paint

I-LCP ikala ukuthi imiphi umsebenzi ophakathi kwekhasi lakho ifinyelela ikusasa ngokushesha. "Okuqukethwe okukhulu" ngokuvamile kuyisithombe sakho sokuqinisekisa, isihloko esikhulu, noma ibhulokhi enkulu ye-above-the-fold.

Izinkinga ezivamile ze-LCP nezixazululo:

ProblemImpactFix
Isithombe sokuqinisekisa esingathuthukisiwe+2-5sIfomethi ye-WebP, usayizi ofanele, fetchpriority="high"
I-CSS/JS ecofwayo+1-3sInline critical CSS, defer non-critical
Ukuphendula kwe-server okweqile (TTFB)+1-4sCDN, ukugcina insiza, ukuhanjiswa kwase-edge
I-web fonts ivimba ukulayisha+0.5-2sfont-display: swap, preload critical fonts
Izikhangiso zezithathu+1-3sDefer analytics/chat widgets, lazy load ads

I-LCP optimization priority:

<!-- 1. Preload the LCP image -->
<link rel="preload" as="image" href="/hero.webp" fetchpriority="high">

<!-- 2. Inline critical CSS (first 14KB) -->
<style>/* Above-the-fold styles only */</style>

<!-- 3. Defer non-critical CSS -->
<link rel="stylesheet" href="/full.css" media="print" onload="this.media='all'">

<!-- 4. Hero image with explicit dimensions -->
<img src="/hero.webp" width="1200" height="600"
     fetchpriority="high" decoding="async"
     alt="Descriptive alt text">

Quick win: Run PageSpeed Insights on your homepage. Look at the LCP element it identifies. If it's an image, convert to WebP, set explicit width/height, and add fetchpriority="high". This alone often drops LCP by 1-2 seconds.

INP — Interaction to Next Paint

I-INP ikala ukuthi ikhasi lakho liphendula ngokushesha kakhulu uma abasebenzisi behlangana (chofoza, bhala, tipe). Ilandelela ukuthinta okubi ngesikhathi sokuvakasha kwekhasi bese iyisebenzisa njengemiphumela.

Izinkinga ezivamile ze-INP nezixazululo:

ProblemImpactFix
Imisebenzi ye-JavaScript ende+200-1000msPhula sibe yimisebenzi encane, sebenzisa requestIdleCallback
Abaphathi bezigameko abaphakeme+100-500msDebounce, throttle, sebenzisa requestAnimationFrame
Ukuqanda kokubuka+50-300msBatch DOM reads/writes, sebenzisa will-change
Izikhangiso zezithathu+100-500msDefer, load after interaction, use Web Workers
Ukuze kudingekwe ama-API+200-2000msAsync/await, loading states, optimistic UI

I-INP optimization techniques:

// Bad: Blocks main thread
button.addEventListener('click', () => {
  const data = heavyComputation(); // Blocks for 400ms
  updateDOM(data);
});

// Good: Yields to main thread
button.addEventListener('click', async () => {
  // Show immediate feedback
  button.textContent = 'Loading...';

  // Break heavy work into chunks
  await scheduler.yield();
  const data = heavyComputation();

  await scheduler.yield();
  updateDOM(data);
});

Quick win: Open Chrome DevTools > Performance tab. Click through your site and look for "Long Tasks" (red triangles). These are blocking the main thread. The biggest long task is usually a third-party script — defer it or load it after first interaction.

CLS — Cumulative Layout Shift

I-CLS ikala ukuzinza kokubona — kahle kangakanani okuqukethwe kukhasi kuziphanshu ngokuphathelene ne -kubukekwa. Akukho okuthandekayo kubasebenzisi kunokuchoboza inkinobho nokuhamba kabusha, bese kudlula kokuningi abakhana.

Izinkinga ezivamile ze-CLS nezixazululo:

ProblemCLS ImpactFix
Izithombe ezingenawo ububanzi0.1-0.5Ngaso sonke isikhathi setha width ne height
Izikhangiso eziqhamuka tarde0.1-0.3Bamba indawo ngenhloso ye min-height
I-web fonts enobukhona ibhalela0.05-0.2font-display: optional noma esikhundleni esilungiswe ngosayizi
Ukufaka okuqukethwe okushintshashintsha0.1-0.4Bamba indawo, sebenzisa content-visibility
Ukuphawula ngama-cookie kuqamba okuqukethwe0.05-0.2Ukuklama kwama-overlay (hhayi ukufaka phansi)

I-CLS prevention checklist:

<!-- Ngaso sonke isikhathi kumele ucacise ububanzi bezindlela -->
<img src="photo.webp" width="800" height="600" alt="...">
<video width="1280" height="720"></video>
<iframe width="560" height="315"></iframe>

<!-- Bamba indawo yokuphawula kwedatha -->
<div style="min-height: 250px;">
  <!-- Isikhangiso sizolanda lapha ngaphandle kokufaka phansi -->
</div>

<!-- Sebenzisa i-aspect-ratio yemidiya efanelekayo -->
<div style="aspect-ratio: 16/9;">
  <img src="..." style="width: 100%; height: 100%; object-fit: cover;">
</div>

Quick win: Add explicit width and height attributes to every and on your top 10 pages. This single change eliminates the most common CLS issue — images loading and pushing content down.

2. Ukuthuthukiswa kwe-Mobile

I-Google isebenzisa ukulungiswa kokuthuthukiswa kwezokuthutha – ubuqotho bakho bomsebenzi be-Mobile YIHLOBO lakho lokubeka. Uma i-site yakho iphukile kumafoni, akubalulekile ukuthi ingabe inguqulo ye-desktop iphelele kangakanani.

I-mobile optimization checklist:

ElementRequirementCommon failure
Viewport metawidth=device-width, initial-scale=1Ukungabikho ngokuphelele
Touch targetsUbukhulu obuncane 44x44pxIzixhumanisi ezincane, izinkinobho ezibuhlungu
Usayizi wezincwadiUbukhulu obuncane be-16px emibhalweni12px engafundeki kumafoni
Ububanzi bokuqukethweAkukho ukukhanukaza kokuhambaIzinto eziphethe ububanzi obunzima
Ukujula kokushaya8px ubuncane phakathi kwezithakazeloIzixhumanisi ezikhatshana zikhanyekwa
Izithombe eziphendulayosrcset ngezinga elifaneleIzithombe ezinkulu kumafoni

Izithakazelo ze-Responsive design:

/* Umqondo ophendulayo kuqala */
.container {
  padding: 16px;
  font-size: 16px;
}

/* Iziphakamiso ezithokozisayo */
.button, .link {
  min-height: 44px;
  min-width: 44px;
  padding: 12px 16px;
}

/* Imibhalo ephendulayo */
h1 { font-size: clamp(1.5rem, 4vw, 3rem); }
p { font-size: clamp(1rem, 2vw, 1.125rem); }

/* Akukho ukusatshiswa okuhamba ngokuhamba */
img, video, iframe {
  max-width: 100%;
  height: auto;
}

Izimpawu ze-Mobile SEO i-Google ehlola:

  • Umbhalo ofundeka ngaphandle kokuzungeza
  • Izixhumanisi/imiyalelo ezidonsele ekuhlakanipheni
  • Okuqukethwe kuhambisana nobubanzi be-viewport (akukho ukudonswa okuhamba)
  • Akukho Flash noma ubuchwepheshe obungaxhunywanga
  • Izinyathelo ezithakazelisa azikuvimbela okuqukethwe lapho ufika
  • Ikhasi ladelekuze liqhubeke nge-4G/3G

Quick win: Open your site on your phone. Try to click every button and link. If you accidentally tap the wrong thing because targets are too close, or if you need to pinch-zoom to read text — those are your priority fixes.

3. Ukufinyeleleka (WCAG)

Ukufinyeleleka akukhona nje okwenziwa ngezinto — kodwa kuyinsiza ye-SEO. I-algorithms ye-Google ithanda ama-site anokufinyeleleka kubo bonke, kubandakanya abasebenzisi abanemishini yokufunda, ohamba nge-keyboard kuphela, noma abangenazinkingtshi. Ukuvumelana ne-WCAG (Web Content Accessibility Guidelines) kuhambisana nezinkomba ezinhle.

Izidingo eziphakeme zokufinyeleleka:

ElementRequirementSEO impact
Alt text on imagesUmbhalo ochaza zonke izithombe ezinemininingwaneNgqo (image SEO + ukufinyeleleka)
Ukuhlela izihlokoH1 → H2 → H3 ngaphandle kokushiyaNgqo (ukwakheka kokuqukethwe)
Ukuhlukaniswa kwemibala4.5:1 ukuze kube umbhalo ojwayelekile, 3:1 ukuze kube umbhalo omkhuluNgaphandle (ukusebenza)
Ukuhamba nge-keyboardZonke izinto ezisebenzisanayo zifinyeleleka nge-TabNgaphandle (ukusebenza)
Amathebhu e-ARIAAmathegi ezithombe, izinkinobho ngaphandle kwemiyaloNgaphandle (i-UX yomshini yokufunda)
Ukuhloseka kokugxilaUmugqa obonakalayo wokugxila kokuhamba nge-keyboardNgaphandle (ukusebenza)
Izincwadi zezinhlawuloUkufaka enye into ohlelweni we Ngaphandle (ukusebenza)
Umbhalo wezixhumanisiUchaza (hhayi "chofoza lapha")Ngqo (anchor text SEO)

Inqubo yokuhlola ukufinyeleleka:

  1. Ukuhlola okuzenzakalelayo — Run Lighthouse, axe-core, or WAVE (catches ~30-50% of issues)
  2. Ukuhlola nge-keyboard — Thola yonke i-site yakho usebenzisa kuphela i-Tab, Enter, Escape
  3. Ukuhlola umshini wokufunda — Sebenzisa i-VoiceOver (Mac) noma i-NVDA (Windows) kumakhasi abalulekile
  4. Ukuhlola umphakathi — Bheka zonke izincwadi ezivela emibhalweni (sebenzisa i-DevTools contrast checker)
  5. Ukuhlola ukusatshisa — Shintsha u-200% — ingabe konke kusebenza?

Izixazululo ezivamile zokufinyelela:

<!-- Izithombe: Umbhalo ochaza -->
<img src="chart.png" alt="Bar chart showing 40% increase in organic traffic from January to March 2026">

<!-- Izinkinobho: Imiyalelo ecacile -->
<button aria-label="Close navigation menu">
  <svg>...</svg> <!-- Inkinobho ye-icon yodwa idinga i-aria-label -->
</button>

<!-- Iziqu: Amathegi ahlokkwe -->
<label for="email">Ikheli le-imeyili</label>
<input type="email" id="email" name="email" required>

<!-- Izixhumanisi: Umbhalo ochaza -->
<a href="/guide">Funda i-SEO guide ephelele</a>
<!-- HHAI: <a href="/guide">Chofoza lapha</a> -->

<!-- Ukweqa ukuhamba kwe-bhodi yama-keyboard -->
<a href="#main-content" class="skip-link">Skipa ekhalanga eliyinhloko</a>

Quick win: Run Lighthouse on your homepage with the Accessibility category. Fix everything scored "Fails" first — these are usually missing alt text, missing form labels, and low contrast text. These fixes often take 30 minutes and improve your score by 20+ points.

4. Izimpawu Zokuhlangenwe Nakho Kwekhasi

Ngaphezu kwe-Core Web Vitals, i-Google ibheka ezinye izimpawu zokuhlangenwe nakho kwekhasi ezingathinta izinkomba.

Izici zokuhlangenwe nakho kwekhasi:

SignalRequirementCheck
HTTPSI-site yonke ikhuluma nge-HTTPSOkuhlangene kubhekisela kuleso simo
Akukho izinyathelo ezithakazelisaUngavimbi okuqukethwe lapho ufikaIzikhangiso ezibamba >30% kumafoni
Ukuhamba okuphephileAkukho malware, lokho kugebengu, okuqukethwe okungafaneleIsimo sokuqapha i-Google Safe Browsing
Ukuthuthukiswa kwe-mobilePasses mobile-friendly testI-Google Mobile-Friendly Test
Akukho izikhangiso ezidukisaIzikhangiso azizifani nezinhleloIzinkinobho zokulanda ezibukekayo

Imihlahlandlela ye-Interstitial (lokhu okukhona vs. okuphikiswa):

KukuvumaKubhujiswa
Ukuqinisekisa ubudala (okuphathelene nomthetho)I-pop-up ephelele ekufikeni kwekhasi
Ukuvuma amakhuki (okuphathelene nomthetho)Ukubhalisela i-imeyili okuhamba yonke imininingwane
Izithiyo ezivela kumakhasi alindelekayo"Landa uhlelo lwethu" kuvimba okuqukethwe
Amabhana amancane azikhipha <30% yesikhalaIzikhathi zokubala ngaphambi kokufinyelela okuqukethwe
Ngemuva kokuhamba komsebenzisiNgaphambi kokuthi umsebenzisi abone noma yini

I-HTTPS checklist:

  • [ ] Isitifiketi se-SSL siyasebenza futhi asiphelile
  • [ ] Zonke amakhasi abuyekeze i-HTTP → HTTPS (301)
  • [ ] Akukho okuhlangene (HTTP resources on HTTPS pages)
  • [ ] HSTS header enabled (with includeSubDomains)
  • [ ] Internal links use HTTPS (not HTTP)
  • [ ] Sitemap uses HTTPS URLs
  • [ ] Canonical tags use HTTPS

Quick win: Check for mixed content — open DevTools Console on your key pages. Any "Mixed Content" warnings mean you're loading HTTP resources on an HTTPS page. Update those URLs to HTTPS. This is one of the most common page experience issues.

5. Izithakazelo Zokuhamba

Ukusebenza kahle kokuhamba kusiza bobabili abasebenzisi nabahloli. Abasebenzisi bayozele indawo abadinga ngayo masinyane. Abahloli be-Google baqonda ubunjalo buka-site bakho futhi bahlukanise iPageRank ngempumelelo.

Imikhuba emihle yokuhamba:

PatternBenefitImplementation
Ubulili obucacileAmakhasi angaphansi kokuhamba okukhona kwezinyatheloAmakhasi amaphakathi, imithombo
Imigqa yokuhambaAbasebenzisi bazi lapho bekhonaSchema markup + umugqa obonakalayo
Ukuhleleka kwendlelaIzindlela ezilindelekayo/category/subcategory/page
Ukuhamba kwe-footerAmakhasi wesibili atholulekileUmthetho, mayelana, uxhumano, isikhumbuzo
Ukusesha kwaphakathiAbasebenzisi bathola okuqukethwe okukhethekileIsikhala sokusesha esinama-suggestion
Okuqukethwe okuhlobeneKwehlisa ukubhampa, kwandisa ukujula"Izindatshana ezihlobene"

Ubulili obuhle be-site:

Ikhasi lezeMbali (1 isinyathelo esivela kukho konke okubhaliwe)
├── /imikhiqizo/ (umoya wekhadi - izixhumanisi zazo zonke izinkanyezi)
│   ├── /imikhiqizo/ubunjalo-a/
│   │   ├── /imikhiqizo/ubunjalo-a/umkhiqizo-1
│   │   └── /imikhiqizo/ubunjalo-a/umkhiqizo-2
│   └── /imikhiqizo/ubunjalo-b/
├── /blog/ (umoya wokuqukethwe - izixhumanisi kuzo zonke izindatshana)
│   ├── /blog/isigaba-sezihloko-1/ (iphepha le-pillar)
│   │   ├── /blog/i-subtopic-1a
│   │   └── /blog/i-subtopic-1b
│   └── /blog/isigaba-sezihloko-2/
├── / amathuluzi/ (amakhasi ezinsizakalo)
└── /mayelana/ (amakhasi ethu)

Ukuphathwa kwemigqa yokuhamba:

<!-- Ukuphathwa kwemigqa yokuhamba -->
<nav aria-label="Breadcrumb">
  <ol>
    <li><a href="/">Ikhaya</a></li>
    <li><a href="/blog/">Blog</a></li>
    <li aria-current="page">SEO Umhlahlo Isinyathelo 5</li>
  </ol>
</nav>

<!-- Schema markup (BreadcrumbList) -->
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    { "@type": "ListItem", "position": 1, "name": "Ikhaya", "item": "https://example.com/" },
    { "@type": "ListItem", "position": 2, "name": "Blog", "item": "https://example.com/blog/" },
    { "@type": "ListItem", "position": 3, "name": "SEO Umhlahlo Isinyathelo 5" }
  ]
}
</script>

Izimpawu ze-red flags zokuhamba:

  • Amakhasi angaphezu kwezinyathelo ezine ukusuka kukhasi lekhaya (kunzima kakhulu)
  • Akukho imigqa yokuhamba (abasebenzisi ne-Google bangenza izihloko)
  • Ukuhamba kwe-JavaScript kuphela (abahloli bangathola izixhumanisi)
  • Amakhasi e-orphan (akukho izixhumanisi zangaphakathi ezibuyela kuzo)
  • Ukuhamba kwe-mega ngemikhawulo engama-200+ (kwehlisa inani le-per-link)

Quick win: Check your most important conversion pages — how many clicks from the homepage? If more than 3, add direct links from your homepage or category hubs. Every click deeper reduces both user visits and crawl frequency.

6. Ukuthuthukiswa Kwe-Above-the-Fold

Lokhu abakukubona ngaphambi kokushelelela kukhombisa ukuthi bahlala noma baphuma. Okuqukethwe kwe-Above-the-fold kufanele kufakazele inani ngokushesha futhi kuhambisane nephutha le-search elibafakele khona.

Izimfuneko ze-Above-the-fold:

ElementWhyCommon failure
Isihloko esicacile (H1)Kuqinisekisa ukuchaneka kokhondoOkuphambana nokuphikiswa
I-Value propositionKungani kufanele bahlale?Ukubhidla ngaphantsi
I-CTA eyinhlokoYini okufanele benze enye?Ukufihla noma ukudideka
Isithombe/sithombe se-heroUkubandakanya okuhlolaUkushesha kokulayisha, kudala izinkinga ze-LCP
Izimpawu zokwethembekaKungani kufanele bakwethembe?Akukho ama-log, ukubuyekwa, noma izitifiketi

Izindlela zokuthola ngaphresident:

Khubaza (1440px viewport):
┌──────────────────────────────────────┐
│ Ibhodwe lokuhambisa                     │
├──────────────────────────────────────┤
│                                      │
│  H1: Isihloko esicacile esihambisana nekhodi  │
│  Isithombe: I-Value proposition         │
│                                      │
│  [I-CTA Button]                        │
│                                      │
│  Izimpawu zokwethembeka: ama-log, izibalo, izitifiketi │
│                                      │
├──────────────────────────────────────┤
│ ↓ Okuqukethwe kuqhubeka ngaphakathi    │
└──────────────────────────────────────┘

Mobile (375px viewport):
┌────────────────────┐
│ I-nav (hamburger)  │
├────────────────────┤
│                    │
│ H1: Isihloko       │
│ (shorter on mobile)│
│                    │
│ [I-CTA Button]     │
│ (full-width, 44px+)│
│                    │
│ Isikhumbuzo sokwethembeka │
│                    │
├────────────────────┤
│ ↓ Shintshela izinkanyezi  │
└────────────────────┘

Imithetho ye-Above-the-Fold:

  • I-H1 kumele ibonakale ngaphandle kokushelelela (ihambisana nekhodi ye-search)
  • I-CTA kumele ibonakale ngaphandle kokushelelela (kwehlisa ukukhuphuka)
  • Akukho ukushintshashintsha kumkhiqizo ose-Above-the-fold (i-CLS killer)
  • Isithombe se-hero kumele sisheshise (ngokuvamile ngoba iyisici se-LCP)
  • Mobile: Nciphisa okuqukethwe kwe-Above-the-fold (ukuthola isikhala se-viewport)

Quick win: Take a screenshot of your homepage on mobile (375px width). Is the H1 visible? Is a CTA button visible? Can you tell what the site does within 2 seconds? If any answer is "no," you're losing visitors before they scroll.

I-UX Audit Checklist

Bheka la kumakhasi akho aphezulu:

  • [ ] I-LCP ingaphansi kwe-2.5 seconds (isithombe sokuqinisekiswa sithuthukisiwe, i-CRITICAL CSS in-lined)
  • [ ] I-INP ingaphansi kwe-200ms (akukho imisebenzi ye-JavaScript ende evimba ukuncintisana)
  • [ ] I-CLS ingaphansi kwe-0.1 (konke izithombe zinemingcele, akukhona ukushintsha okuza)
  • [ ] Kufanele kube mobile-friendly (44px touch targets, 16px+ text, akukhona ukudonswa)
  • [ ] Ukufinyeleleka (umzimba wezithombe, ukuhlela izihloko, ukuhamba kwephezulu, ukuhamba nge-keyboard)
  • [ ] HTTPS yonke indawo (akukhona okuhlangene, i-HSTS ivuliwe)
  • [ ] Akukho izinyathelo ezithakazelisa (ukuvuma kokuwa kulungile, izikhangiso ezivimba okuqukethwe)
  • [ ] Imigqa yokuhamba ikhona (ngokuhambisana ne-BreadcrumbList schema)
  • [ ] Ukuphindaphinda kokuhamba kukhulu kwezinyathelo ezivela kukhasi elikhulu
  • [ ] Ukuthuthukiswa kwe-Above-the-fold (i-H1 ibonakala, i-CTA ibonakala, i-LCP esheshayo)

Indlela i-LANGR Ihlola i-UX Yakho

Amamojuli okulanda uxhumano lwe-UX behlola:

  • Module ye-Core Web Vitals — Mejezela i-LCP, INP, CLS ukusuka ku-Chrome User Experience Report (idatha yomsebenzisi)
  • Module ye-PageSpeed — Ukugcina ukuhamba okugcwele kwamahhala kwe-lighthouse ngezenzo ze-mobile ne-desktop
  • Module ye-Mobile — Ukulungiswa kwemikhawulo yokubuka, usayizi wezindawo zokuthinta, ukufunda kombhalo
  • Module yokuFinyeleleka — Ukuhlola ukuvumelana kwe-WCAG, izinzwa ze-ARIA, ukuhlakanisa kwembala
  • Module ye-Layout Scan — Ukuhlola kwezobuchwepheshe okucaphelayo kwe-mobile ne-desktop
  • Module ye-Page Experience — Ukuqinisekisa ukungena, isimo se-HTTPS, ukuhamba okuphephile

Le maphutha yokuhlola ibona umfanekiso ophelele wokuthi abavakashi bahlola i-site yakho kanjani — kanye nendlela yokulungisa engcono yokubeka.

Iziphazamiso Eziyinqaba ze-UX (Zibhalwe ngokuKwaziswa)

  1. Ukunganaki i-mobile — I-60% + yokuhlola ku-mobile; iphukile i-mobile = uqhubekela phansi izinkomba
  2. Izithombe ezingathuthukisiwe — Umphumela ophakeme we-LCP (futhi ngokuvamile kulula ukusiza)
  3. Akukho ububanzi bamatayela ezithombe — Ukushintshashintsha kwe-imikhawulo kudalulekile
  4. I-Third-party script bloat — Izinsiza zokuxoxa, ama-analytics, izikhangiso ze-inp ezikhethiwe
  5. Missing accessibility basics — Akukho ama-alt text, akukho ukuhlela kwe-headers, akukho mhlangano
  6. Izinyathelo ezivimba okuqukethwe — I-pop-up ephelele ngaphambi kokuthi abasebenzisi babone okuqukethwe
  7. Ubulili obunzima bokwakha — Amakhasi abalulekile aqhutshwa ngaphezulu kwemigqa eminingana
  8. Akukho inani le-Above-the-Fold — Abasebenzisi abakwazi ukuchaza ukuthi i-site ibhekiwe ngaphandle kokushelelela

Okulandelayo?

Isinyathelo 6: Ukubhekisisa & Ukubeka — Awukwazi ukuthuthukisa okufanele ungakwenzi.


Le mhlahlandlela ingxenye ye-LANGR's 13-step SEO series. Qhubekani uphumelele ukubona ukuthi i-site yakho ihle kanjani phakathi kweziqondisi eziyi-13.

Want to know where your site stands?

Run a free SEO audit — it takes under 60 seconds.

Related articles