Test your day care's website speed in 20 minutes (the same way we measured every one in Tiverton)

If you run a day care in Fall River, Somerset, or Swansea, your website is doing a job you probably never think about. A parent with a newborn and a return-to-work date is on their phone at 10pm, comparing three centers. They are not reading every word. They are getting a feeling in the first two seconds: is this place organized, warm, and still open? If your page is still a blank white screen while they wait, you lose that feeling before a single photo of your classroom loads.

The good news is that this is measurable, it is fixable, and Google gives you the exact tool for free. This is a walkthrough. By the end you will have tested your own site the same way a professional would, you will understand the one number that matters, and you will have done at least one repair yourself without paying anyone. It takes about twenty minutes.

First, the respect part#

Day cares in this region are, by and large, excellent at the thing that counts. Just over the line in Tiverton, the four independent day cares Google lists hold forty reviews between them and average 4.76 stars, none below 4.2. Those are not numbers you can buy. They come from years of parents trusting you with the most precious thing they own and coming back to say thank you in public. Most of these centers have waitlists.

So this is not a lecture about your business. It is a look at one quiet, fixable leak in the front of it. When we ran every one of those four Tiverton day care websites through Google's speed test, here is what a parent's phone actually experienced:

Those are lab measurements from Google PageSpeed Insights, taken on 21 July 2026. Every one can be re-run by anyone, which is exactly what this walkthrough is going to teach you to do.

The one number that matters: LCP#

You do not need to learn the whole vocabulary of web performance. You need one term. It is called Largest Contentful Paint, or LCP, and it measures the moment the biggest piece of your page (usually your main photo or headline) actually shows up on the screen. It is the closest thing there is to "how long the visitor stared at nothing."

Google is not vague about the target:

To provide a good user experience, sites should strive to have Largest Contentful Paint of 2.5 seconds or less.

Under 2.5 seconds is "good." Over 4.0 seconds is "poor." Everything in between "needs improvement." Here is how the four anonymized Tiverton day cares scored, worst leak last:

Read that against the star ratings and the point lands: these are well-loved businesses whose websites are quietly working against them. Site D has a perfect rating and a website that makes a parent wait thirteen seconds. Almost none of them, by the way, had any analytics installed, which is usually why it stays broken. Nobody is measuring it, so nobody knows.

Let us fix that for your site, right now.

Step 1: Test your own site (3 minutes, free)#

Open your phone or computer and go to pagespeed.web.dev. That is Google's own tool, the same engine that produced every number above.

Type in your website address and press Analyze. Wait maybe thirty seconds. When the report loads, do two things and ignore everything else:

1. Make sure you are looking at the Mobile tab at the top, not Desktop. Most parents find you on a phone, and phones are slower. Desktop will flatter you and lie.
2. Scroll to the colored dials and find Largest Contentful Paint. Read the number in seconds.

That number is your answer. Under 2.5 and green, you are in rare and excellent company. Between 2.5 and 4.0 and orange, there is easy work to do. Over 4.0 and red, a measurable share of parents are giving up before your page appears. Write your number down. You now know something three of the four day cares up the road do not know about themselves.

Step 2: Find out why (2 minutes, free)#

Right below the score, PageSpeed Insights lists the reasons, in order of how much time each is costing you. For a small local website, the top of that list is almost always the same culprit: an oversized image.

Here is what happens. Someone (a nephew, a template, a well-meaning designer) put your lovely classroom photo on the homepage straight off a phone camera. That file is four or five thousand pixels wide and several megabytes. On a parent's phone over cell service, the browser has to drag that whole enormous file down before it can show the picture, and the picture is the biggest thing on the page, so LCP waits for it. Your site is not slow because it is complicated. It is slow because it is carrying a suitcase full of pixels nobody can see.

Look for a line in the report that says something like "Properly size images" or "Efficiently encode images," with a number of seconds next to it. That is your free money.

Step 3: The fix you can do yourself today (15 minutes, free)#

You do not need a developer for this. You need to shrink the image and hand the smaller one back to whoever manages your site.

Go to squoosh.app, a free image tool made by Google's Chrome team. Drag your homepage photo onto it. On the right, you will see a slider and a live preview:

• Set the format to WebP (a modern format that is far smaller for the same quality).
• Drag the quality slider down to around 75. Watch the preview. You will usually see no difference at all, while the file size at the bottom drops by 80 or 90 percent.
• If there is a resize option, set the width to around 1600 pixels. No phone screen needs more than that for a homepage photo.
• Download the new file.

That single swap, a two-megabyte photo for a 150-kilobyte one, is frequently the whole difference between a red score and a green one. If you can update your own site (Wix, Squarespace, WordPress, GoDaddy all let you replace an image in a few clicks), do it now and re-run Step 1 to watch the number fall. If you cannot, email the smaller file to whoever built your site with one sentence: "Please replace the homepage image with this smaller version." It is a five-minute job for them.

What to hand off, and what to leave alone#

Some things on that PageSpeed report are genuinely a developer's job: server response time, render-blocking scripts, the guts of your theme. Do not try to hand-edit code you do not understand, and do not let anyone talk you into a full rebuild to fix a slow image. Redesigning a whole website because one photo is too big is like buying a new car because the tires are flat. The image fix above, done properly, moves the number that Google actually ranks on, and it costs nothing but twenty minutes.

If your LCP is still red after you have compressed the hero image, that is the honest signal that something deeper is going on, and that is a worth a real conversation. But you will be having it from a position of knowledge, with your own measured number in hand, which is a much better place to negotiate from than a sales pitch.

Your Monday#

Before you open the doors Monday: run pagespeed.web.dev on your own site, on the Mobile tab, and write down your LCP. If it is over 2.5 seconds, take your homepage photo through squoosh.app and either swap it yourself or send the smaller file to your web person. That is a free, twenty-minute morning that most of your competitors have never done, because nobody ever showed them the number.

If you would rather hand the whole thing to someone local who does this for South Coast small businesses every week, that is what Avalon is for. I will run the test, do the fixes, and put analytics in place so you actually see the difference, and I will tell you plainly if your site is already fine and does not need me. Call Joshua at 774.559.8992 or email Joshua.Amado@AvalonPartner.com.