In the infant years of Google, they wrote ten things we know to be true. One of those core principles is that fast is better than slow. Speed matters. We all live busy lives. Even when we’re not busy, we don’t want to spend our leisure time waiting for something else. In e-commerce, information delivery, or service explanations, website visitors want to find what they need as fast as possible.
Other research has shown a correlation between measured page speed and the number of conversions on a website: slower sites get less conversions.
Google has consistently stated that page speed, particularly for mobile, is a ranking factor. They understand that their users are happier when they navigate away from search, the website actually loads with content.
Ensuring that their users feel like they can trust the first click away from Google is their priority. New technologies from Google push the envelope on first-click speed with accelerated mobile pages (AMP), for example.
We all love beautiful imagery on a site. However, when it is too big, it can slow down your site unnecessarily. What’s too big? Well, whenever there’s a significant difference between the intrinsic size of the image (how big the file is) versus the rendered size (how big the file appears), you’re spending too much time loading that image.
Websites by their nature want to deliver content over the web, but sometimes they don’t have to. When someone has visited your site or loaded a page, that information can be cached by the user or by a CDN to avoid costly round trips to your server and back. Do it right once, then it won’t need to be repeated.
A big culprit to poor user experience is a layout shift after some content has loaded. Interrupting the user from reading the content on your site by making those big page jumps we’ve seen on news sites loading display ads in the middle of their content is jarring and annoying. Avoid headers or display ads that push around content for the user so that they can read the content that loads without interruption.
Sometimes, websites are busy loading content that isn’t within the viewport – the area of the screen that requires scrolling to load. Prioritizing content that is within the first load area will get content to the site visitor faster.
First, the Leadbox is designed to load asynchronously from your site. Also, it isn’t “required” before or while you’re trying to load the content on your site. That means, your site and its content will load first, then the Leadbox will load once your site is done.
Visitors to your site, even returning visitors, usually need a second or two to see that they’ve landed in the right place and want to contact you. They take a quick look at the content on the page, feel it is trustworthy, and then choose to interact with you.
The Leadbox widget loads to catch the site visitors eye after they have done that initial gut-check on your site. The loading a second or two after page load, along with the animation of our secondary call-to-action (CTA) button, catch the prospects attention and lead them to interact. That’s just what you want.
Design tip: with the Leadbox, you’ll want to avoid a footer without extra padding to accommodate the Leadbox CTAs. That way, site visitors can always scroll to the bottom of the page and read all your site content.
Once those CTAs load, the interaction is fast, because the Leadbox is processing client-side, which means, the site visitor isn’t waiting for something from a server to submit the lead information: name, mobile number, and message. It’s all there, ready for them to submit.
Lighthouse is part of Chrome’s developer tools and can be accessed directly from your Chrome browser. The performance report displays the page speed metrics. These metrics, summarized below the sample screenshot of a Lighthouse report, touch on the core principles mentioned above.
When FCP is fast, site visitors aren’t staring at a blank screen wondering if your site is still loading.
When SI is slow, it seems like things are taking awhile to load.
When you have one thing that is slowing down your site, you’ll see that increase LCP.
When TTI is slow, you can’t do things like scroll the page.
TBT is a factor when one image or widget is blocking other things from being able to load.
When something like a sticky header loads after the content below it, you’ll see the page shift and take you away from whatever you were reading with there’s a significant CLS.
The Leadbox avoids many of the pitfalls found in slow sites:
When running Lighthouse on a webpage that only loads the Leadbox over the network, the score is perfect.
When running Lighthouse on live web pages, the score can fluctuate based on network conditions, sometimes swinging as many as eight to nine points, but, ultimately, the Leadbox impact on that score is negligible.
Here is an example of a base WordPress install with and without the Leadbox installed. On the left you see this WordPress site with a performance score of 100. On the right we have added the Leadbox widget using the Leadbox WordPress plugin and the score was impacted by a point and is now a 99.
Now that you know the Leadbox doesn’t impact your website speed you can take advantage of faster communication. Bringing text messaging to your business and as a conversion tool on your website is a speed and experience win across the board.
Note: If you are using a speed optimization tool or service like NitroPack, WP Rocket or similar you’ll want to make sure not to block the Leadbox code. Contact email@example.com for further help.
Get our monthly update covering SMS, messaging, and Leadferno features.