Skip to content

Audit record 7 min read Updated September 23, 2026

A heavy page-builder theme was quietly turning every mobile visit into a long wait

In short

A Christian preschool serving families across the Dallas-Fort Worth, Texas metro ran its site on a common website builder platform whose theme and page-builder plugin combination loaded a large hero photo and two separate tracking bundles before the page became usable. On a phone, that added up to a wait measured in double-digit seconds before a visitor could do anything at all.

Key facts

  • A mobile performance test of the homepage returned a score in the failing range, with the page's main content taking well into double-digit seconds to become visible.
  • A large, uncompressed hero photograph was the single biggest contributor to the page's total weight, loaded at full size regardless of the visitor's screen.
  • Two separate tracking and analytics bundles were loading on every page view, adding meaningful weight without either one being clearly necessary on its own.
  • The page also shifted visibly while loading, elements jumping position as later content arrived, which is its own separate, measurable usability problem beyond raw load time.
  • The platform's own on-page technical basics, like page titles and descriptions, were generally handled well, which meant the slowdown was specifically a weight and configuration problem, not a broader neglect of technical setup.

The finding

This site ran on a widely used website-builder platform, paired with a popular visual page-builder plugin, a combination that makes building a page easy but can quietly load far more code and imagery than a page actually needs.

On a phone connection, that combination added up to a genuinely long wait before the page became usable, well into double-digit seconds by the time the main content settled. A visitor on a real phone, on a real connection, experiences that wait directly, often abandoning the page before it finishes loading at all.

What we looked at

We ran a standard mobile performance test against the live homepage and recorded the overall score along with the specific metric measuring how long it took for the page's main content to become visible. Both came back in a range generally considered a real problem, not a minor inefficiency.

We then broke down exactly what was contributing the most weight to the page, and found one oversized hero photograph and two separate tracking or analytics scripts responsible for a large share of the total. We also noted visible layout shifting as the page loaded, a second, related usability issue beyond pure speed.

Why it mattered for leads

Most visitors researching a preschool for their child are doing it on a phone, often while managing other things at the same time, and a page that takes many seconds to become usable loses a real share of those visitors before they ever see a single word of content.

Slow mobile performance also factors directly into how search engines rank a page, since speed on mobile devices has been a recognized ranking factor for years. This site was quietly losing on two fronts at once: fewer visitors staying long enough to read, and a technical handicap in how visible the page was to begin with.

False positive checks we ran

We reran the performance test more than once and from more than one testing location to rule out a temporary network fluke rather than a consistent, structural problem. The result held steady each time, within a normal range of variation.

We also checked whether the site's broader technical setup was generally neglected, which would suggest this was one symptom of many, or whether it was specifically isolated to page weight and loading behavior. The site's basic technical setup, page titles, descriptions, and general structure, was handled reasonably well elsewhere, which confirmed the slowdown was a specific, fixable configuration problem rather than a sign of a site abandoned entirely.

The fix

The rebuilt site compresses and properly sizes every image for the device requesting it, so a phone never downloads a full-size photo meant for a large desktop screen, and consolidates tracking down to what is actually needed rather than running duplicate, overlapping scripts.

We also addressed the visible layout shifting directly, by reserving space for images and other elements before they finish loading, so the page settles into its final layout immediately instead of jumping around while a visitor is trying to read it.

How to check your own site for this

Run your own homepage through a free mobile performance testing tool and look specifically at how long it takes for your main content to become visible, not just the overall score. A wait measured in double-digit seconds on a phone is a real, immediate problem worth fixing before anything else on the site.

If your site runs on a page-builder platform, it is also worth checking exactly what plugins and scripts are active, since it is common for several tools to be added over time, each for a reasonable individual purpose, that collectively slow the page down far more than any one of them would alone.

Related questions

Real findings from SearchPod proposal reviews, anonymized; platforms change, records are dated.

Want your site audited the same way?

Get a free, no-obligation proposal within one business day. We look at your site and your market and tell you plainly what we would do, and what we would not.

Get your free proposal

Keep reading

More in Audit library

All 40 in Audit library