Definitive engineering academy for SEO, web architecture, and scale.

Pragmatic, step-by-step masterclasses forged in production environments and modern global standards.

Learning track

Site speed

  • 0 lessons
  • Free, no signup

The path, step by step

Lessons are ordered so each stands on the previous one. You can also jump in anywhere.

What the site speed track gives you

From measuring through to fixing the bottleneck. This track has no lessons yet, and we say so plainly.

0lessonsToday
3metricsLCP, INP, CLS
0tomanFree

Tap any step to read the details behind it.

Innovative solutions in the site speed track

Every lesson has the same familiar shape, so you move through easily.

Tap any solution to see exactly what it includes.

Five steps of learning site speed

We set web.dev and Lighthouse beside Seemerce's site-speed track.

1

Measure first

Lighthouse treats the score as a weighted average of several metrics; 90 to 100 is green.

With us The track runs from measurement to fixing the bottleneck.

2

LCP

web.dev: up to 2.5 seconds is good.

With us This track has no lessons yet and we say so.

3

INP

web.dev: up to 200 ms is good and over 500 poor.

With us This track has no lessons yet and we say so.

4

CLS

web.dev: up to 0.1 is good and over 0.25 poor.

With us This track has no lessons yet and we say so.

5

Metric weights

In Lighthouse 10, TBT is 30% of the score and LCP and CLS 25% each.

With us This track has no lessons yet and we say so.

Sources: web.dev; Chrome Lighthouse

Six numbers

Each figure is from its own source.

2.5s or less

LCP · good

The good threshold.

web.dev
200ms

INP · good

The good threshold.

web.dev
0.1or less

CLS · good

The good threshold.

web.dev
90– 100

Lighthouse · green

The good band.

Lighthouse
0lessons

This track today

This track has no lessons yet.

Seemerce
0toman

Free

Free with no sign-up.

Seemerce

Sources: web.dev; Chrome Lighthouse

web.dev and Seemerce

Only what the reference document says outright is marked.

Practiceweb.devSeemerce
LCP threshold1 of 1This threshold will be explained in the track
INP threshold1 of 1This threshold will be explained in the track
CLS threshold1 of 1This threshold will be explained in the track
The Lighthouse score1 of 1This score will be explained in the track

stated on their published page   not stated there (it may still be done)

Sources: web.dev; Chrome Lighthouse

web.dev's good thresholds

Three speed metrics in seconds.

2.5 s0.8 s0.2 s
LCPTTFBINP
All three are measured at the 75th percentile of visitors.

Sources: web.dev — LCP, TTFB, INP

What this page offers

Only what this page already promises.

This track

  • From measurement to fixing the bottleneck
  • No lessons published yet
  • Free with no sign-up

Honesty

  • We show what is not there yet
  • Honest about limits and Iran access
  • Free with no sign-up

Lesson shape

  • Diagrams instead of stock images
  • AI guidance in every lesson
  • Ends on the fastest professional workflow
See+Tempo=SeeTempo This page's name in the Seemerce family What the name means
This page's name in the Seemerce family

Site speed from measurement through to fixing the bottleneck.

The rule is simple: See joins a word to make one new word, just as See and commerce became Seemerce.

Related names