A one hour speed checklist for practice managers
In one hour, without a developer, you can measure your key pages, find the oversized images and unneeded widgets, check hosting and Search Console, and hand your web vendor a short, specific list of fixes. Work in four 15 minute blocks and write down every number with the date.
Before you start: what you need
Gather these before the clock starts:
- A laptop and your own smartphone
- A list of four pages: your homepage, your busiest service or condition page, one location page and the page your Book button opens
- Access to your website editor or media library, if you have it
- Access to Google Search Console, or the name of whoever has it
- A simple document or spreadsheet for results
If you do not know your busiest pages, Search Console's performance report or your analytics will show which pages get the most visits from search. If you have neither, start with the homepage and the service you most want to grow.
Minutes 0 to 15: measure
- Open PageSpeed Insights and test each of your four pages on the Mobile tab.
- For each page, write down whether the Core Web Vitals assessment from real users passes, plus the LCP, INP and CLS values. Note if it shows data for the whole site rather than the page, or no real user data at all.
- Write down the lab performance score, and label it clearly as a lab number.
- Note which element is reported as the Largest Contentful Paint on each page.
- Run the homepage on the Desktop tab too, for comparison.
Lab scores move a little between runs, so if a result looks odd, run it again. What each number means is explained in how to test your website's speed.
Does ChatGPT recommend your practice?
The Surge Score measures five things about your practice website: how often ChatGPT, Gemini and Perplexity recommend you, your PageSpeed, your structured data, your indexing and your reviews, each with its evidence and date. Free.
Minutes 15 to 30: images
- On each page, look at the main photo at the top. If it is the Largest Contentful Paint element, it is your first suspect.
- In your media library, find that file and note its size and pixel width. A hero image measured in megabytes, or thousands of pixels wide, needs a resized, compressed replacement.
- Scan galleries, sliders and before and after pages for the largest files.
- Note any slider or video at the top of a page. Replacing a slider with one strong photo is often a quick win.
- Scroll each page on your phone and watch for jumps as images load.
If you have editing access and a properly sized file, you may be able to fix the hero yourself today. Details are in images and slow websites.
Minutes 30 to 45: widgets, scripts and pop ups
- On your phone, open the homepage and list every widget you see: chat, reviews, booking, maps, video, social feeds, banners and pop ups.
- For each one, ask two questions: has anyone used it in the last three months, and does it bring in bookings?
- Note any pop up that covers the screen on a phone, and anything that appears late and pushes content down.
- If you can see your tag manager or plugin list, note anything unfamiliar or tied to an old campaign.
- Mark each item keep, delay or delete.
You probably will not remove anything in this block. The goal is a list your vendor can act on. Why each item matters is in chat widgets and third party scripts.
Minutes 45 to 60: hosting, Search Console and a real phone
- Test your privacy policy or another plain page in PageSpeed Insights. If even that page is slow to start, note possible hosting trouble; see cheap hosting and what it costs you.
- In Search Console, open the Core Web Vitals report and note any mobile groups marked poor or needs improvement, and which metric is failing.
- Turn off wifi, open a private browser tab, search your practice name and tap through to booking. Time how long until you see real appointment times.
- Do it once more as a new patient searching for a service, starting from Google rather than your homepage.
Write down anything that frustrated you. If it annoyed you, it annoyed patients, and they had less reason than you to persist.
What to send your web vendor
End the hour with a short, specific message. Vague requests get vague work. A useful one includes:
- The four pages tested, with the date and the mobile LCP, INP and CLS for each
- Which pages fail, and which metric fails on each
- The hero and gallery images that are too large, by file name
- The widgets and tags you want removed, delayed or limited to certain pages
- Any pop up or banner that covers content on mobile
- A request for a written plan and a date to retest
Retest the same four pages after the work is done, then monthly. A page that passes today can fail next quarter after someone adds a new widget or tag.
Checklist
- Four key pages tested on mobile, with results written down and dated
- The Largest Contentful Paint element identified on each page
- Oversized hero and gallery images listed by file name
- Every widget and pop up on the homepage listed and marked keep, delay or delete
- A plain page tested to rule hosting in or out
- Search Console's Core Web Vitals report checked for poor mobile groups
- The booking path timed on your own phone over cellular data
- A specific fix list sent to your web vendor with a retest date
Frequently asked
Do I need technical skills for this checklist?
No. Every step uses free tools and your own phone. You are measuring and listing, not changing code. The fixes may need a developer, but the list you produce will save them time and save you money.
How often should I repeat it?
Run the full hour once a quarter, and a short version, the four pages in PageSpeed Insights plus the phone test, once a month. Repeat it after any redesign, new widget or new tracking tag as well.
What if all my pages already pass?
Then keep them passing. Save the results as your baseline, and ask your vendor to test speed before adding any new widget, plugin or tag. Speed usually erodes quietly as features pile up, so the baseline is what lets you notice.
What if PageSpeed Insights shows no real user data for my site?
That is common for smaller practices and does not mean you failed. Use the mobile lab results and your phone test as your guide, and aim for the same thresholds Google uses for real users.
Sources
- About PageSpeed Insights, Google for Developers
- Core Web Vitals report, Search Console Help (Google)
- Web Vitals, web.dev (Google)
- Lighthouse performance scoring, Chrome for Developers
Book a strategy call with the team.
Twenty minutes. We'll walk through the specific opportunities in your market and what a MedPracticeGrowth engagement would look like for your practice.