Skip to main content
FreeThree checks for your projectUptime, accessibility, SEO and cookie checks for your project
All articles

Speed and searchOct 22, 20265 min read

Every page, or one page of each type? How to scan a large website

Valentin ZsigmondFounder & Lead Engineer

A website with a thousand pages was not designed a thousand times. Someone designed an article page, a product page, a list page, a contact page and a few others. Every page since has been poured into one of those moulds.

That changes what it means to check a whole website for accessibility, speed and search engines. You can test every page, or you can test one page from each mould. Lens offers both. This article explains what each setting finds, what it misses, and how long it takes. If the three checks are new to you, start with what one scan of your website tells you.

Most faults live in a page type

A page type is a kind of page that shares its design: an article, a product, the contact page. Most faults sit in the type. If the heading on one article is too pale to read, it is too pale on every article. If a script slows one product page, it slows all of them.

So a full test of one article tells you most of what a full test of every article would. The example on the Lens page is a website of 1,000 pages built from 9 page types. Nine full tests find the shared faults of a thousand pages.

Some faults are not shared. Somebody uploads one very large picture to one page. One article gets a table pasted in from a spreadsheet. These faults live on a single page, and a test of another page of the same type will not see them.

The two settings

You choose how deep Lens goes. It starts with one page of each type, and you can switch at any time.

One page of each typeEvery page
Tested in fullOne page of each type, a different one each weekEvery page
A fault shared by a page typeFoundFound
A fault on one single pageFound when that page has its turnFound
Time for 1,000 pages of 9 typesAbout half an hour20 hours
Search engine checkEvery pageEvery page

One page of each type

Lens tests one page of each type in full. The scan is done in about half an hour and barely touches your website.

The risk is the single-page fault. The page with the very large picture is found when that page has its turn. Lens picks a different page of each type every week, so the turn does come. On a type with many pages it can be a long way off.

For most websites this is the right setting. You hear about the faults that affect the most pages first, and those are the faults worth repairing first: one change to the design repairs every page of the type.

Every page

Lens tests every page in full, and finds every single fault. The cost is time. A website of 1,000 pages is covered in under a day. One of 5,000 pages takes about 4 days.

Choose this if you need each page tested every week and your website is small enough, or if you accept that a large one takes days to cover.

What does not change

With either setting, every page is checked for search engines. A page that tells search engines to stay away, or one that is missing from your sitemap, can be a single page or a whole section, and you want to hear about it either way. Lens sends an alert for both.

Why the pace is gentle

Lens opens about 25 pages every half hour. That is slow on purpose.

A scanner opens a page the way a visitor does, so every page it opens is work for your server, the same as a visit. A scanner that opened thousands of pages as fast as it could would ask for all that work in one burst, and your real visitors would wait behind it. A tool that measures how fast your website is should not be the thing that slows it.

At about 25 pages every half hour, Lens asks far less of your website than a handful of visitors would. Your visitors never notice it.

The two settings follow from that pace. About 25 pages every half hour is about 50 an hour. For 1,000 pages that makes 20 hours. For 5,000 pages it makes about 4 days. Covering a large website faster would mean leaning harder on it. One page of each type is how you get an answer today without that cost.

How often Lens scans

  • On the free plan: 5 pages, once a month.
  • On paid plans: the home page every day, and the whole website every week.

The home page is checked every day, so a serious problem there shows up within a day. After a scan, Lens shows whether each score went up or down. The scores are kept over time, so you can see when a change slowed a page.

The repeat matters as much as the first scan. Websites change, and new problems arrive with new pages. A scan from last spring describes a website you no longer have.

Which one to choose

  1. Start with one page of each type. It is where Lens starts, and it shows you the faults that affect the most pages.
  2. Repair the shared faults first. Each repair covers a whole type.
  3. Then consider every page. Once the shared faults are gone, what remains are the single-page ones: the large picture, the odd table. A scan of every page finds them all. On a small website it costs little. On a large one it takes days, and you can switch back afterwards.

One thing holds for both settings. A scan is automatic, and it finds what a machine can see. Whether a person using a screen reader can get through your order form is a question for a person. That limit is the same however many pages you scan.

The scan settings, and the plans by number of pages, are on the Lens page.

Written by

Valentin Zsigmond

Founder & Lead Engineer

Now check your own project.

Add your project and see what it needs. The first three checks are free.