How to Check Your Website Performance
Need a tool to check your website's performance?
Chrome DevTools has the perfect tool called Lighthouse.
And what a fitting name for a tool that can help light the path.
Lighthouse checks a webpage for Performance, Accessibility, Best Practices, SEO, and Agentic Browsing.
This Field Note looks at what Lighthouse measures, how to read the report, and what those scores can tell you about your website.

How Do You Find Lighthouse?
You don't need to download Lighthouse or pay to use it.
It is available in Chrome DevTools.
Open the webpage you want to check in Chrome, then press F12 to open DevTools.
On a Mac, use Cmd + Option + I. You can also right-click anywhere on the page and select Inspect.
If you are opening DevTools for the first time, Elements will be selected on the toolbar across the top. Select Lighthouse.
Lighthouse will open with options that let you choose how the webpage will be tested, which device to test for, and which categories Lighthouse will check.
What Do the Lighthouse Settings Mean?
Navigation
Timespan
Snapshot
Mobile
Desktop
Performance
Accessibility
Best Practices
SEO
Agentic Browsing
Navigation analyzes the webpage as it loads. It shows what happens during a normal page load.
Timespan measures the webpage while you interact with it over a period of time.
Snapshot examines the webpage as it exists at the moment the snapshot is taken.
Mobile tests the webpage using Lighthouse's mobile settings.
Desktop tests the webpage using Lighthouse's desktop settings.
Performance measures how quickly the webpage loads and becomes usable.
Accessibility checks for issues that can affect how people with disabilities access and use the webpage.
Best Practices checks for issues with the webpage's security, browser compatibility, and how it is built.
SEO checks the webpage for basic issues that can affect whether search engines can discover and index it.
Agentic Browsing checks how well the webpage can support AI agents that interact with websites.
How Do I Generate a Lighthouse Report?
I leave all five categories selected so Lighthouse can check the page across each area.
If I haven't checked any pages on the site yet, I start with the Home page.
If you have extensions installed in Chrome, I recommend opening the webpage in an Incognito window before generating the Lighthouse report.
Browser extensions can add scripts or other activity to the webpage while Lighthouse is testing it, which can affect the report and make it harder to tell whether an issue is coming from the webpage or the browser environment.
Chrome extensions are normally disabled in Incognito unless you have specifically allowed them to run there, which gives Lighthouse a cleaner environment for testing the webpage.
When I first started generating Lighthouse reports, I would run Snapshot on Desktop with all five categories selected, followed by Navigation on Desktop.
After checking Desktop, I would go back through the pages and run the same sequence on Mobile.
I don't do that anymore. I start with Mobile.
So many people view websites on their phones, and Mobile is where I have found Lighthouse most often uncovers the issues that need my attention.
Think about a potential customer standing on the side of the road looking for a business on their phone.
They need the information now. If your website takes too long to load or is difficult to use, they may leave and find another business whose site gives them what they need faster.
Mobile portrait also tends to be the view that needs the most adjusting on my own site, and I have found that fixing those issues often improves Desktop at the same time.
And who doesn't like a fix that only uses one stone?
Generating Lighthouse reports takes time, so I rarely run the same pages through Desktop afterward unless I have a reason to.
For me, Mobile is where the gold mine is.
I don't spend much time with Timespan unless there is something specific on the page I want to test while interacting with it.
I use a college-ruled, one-subject notebook and write down all of the pages I want to check ahead of time.
That's just my preference, but it makes transferring the scores from each report quick.
I date the page so I can refer back to the scores later, and leave some space between each webpage for notes about anything I changed or fixed.
How Do You Read a Lighthouse Report?
After Lighthouse generates the report, each category you selected is given a score. The scores are grouped into three ranges:
90–100 Good
50–89 Needs Improvement
0–49 Poor
The score gives you a quick indication of how the webpage performed in that category.
Below the scores, Lighthouse breaks the report into individual checks so you can see what passed and what may need attention.
Some of the most useful information isn't the score itself. It's what Lighthouse shows you underneath it.
Lighthouse can find issues that aren't immediately visible, such as slow-loading images, layout shifts, accessibility problems, or search engine access issues.
The report identifies the issue and, depending on the check, provides additional information about what Lighthouse found.
This is where Lighthouse becomes especially useful to me.
I enjoy uncovering what lies beneath the site build and using the report to find issues I may not have known were there.
Lighthouse considers a score of 90–100 good, but I set my own bar higher.
Anything below 93 gets my attention, and the lower the score, the more important it becomes for me to find out why.
What Do You Do After Lighthouse Finds an Issue?
Lighthouse identifies the issues it finds and explains what is wrong.
For some issues, it also shows the specific elements or images on the webpage that need attention.
Knowing what the issue is doesn't always mean I know how to fix it.
When the solution isn't clear to me, I get help understanding what needs to be changed and how to make the adjustment.
Would I be ecstatic to see 100 in Performance, Accessibility, Best Practices, SEO, and Agentic Browsing? Absolutely.
But the goal isn't to make changes just to reach 100. It's to understand what Lighthouse found and correct the issues that need correcting.
Once I make a change, I generate another report to see whether it corrected the issue and how the score changed.
I record the new score along with notes about what was changed so I can refer back to it later.
I've had a page that previously scored well suddenly drop to 74. The mystery was that I hadn't made any changes to the page.
I went back through my Lighthouse notes and followed the trail to understand why.
Lighthouse identified the hero image as an issue.
It was set to lazy loading, so I changed it to eager loading and generated another report.
The Performance score went from 74 to 97 with that one change.
That's a good example of why I pay attention to what Lighthouse finds beneath the score.
Sometimes one change can make a big difference.
From Field Tool to Clarify Assessment
Lighthouse can uncover issues you may not have known were affecting your website.
The same can be true of your business.
A Clarify Assessment looks beneath what you see day to day to uncover what may be standing between where your business is now and where you want it to go.
The Path Settings
Choose how this site remembers your preferences.
Analytics Cookies
These cookies help us identify the most useful paths for visitors, allowing us to enhance the user experience while protecting your privacy.

