livepage.net website review

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.8 s.

Your mobile performance score is 89 (desktop: 70). Pages that score under 90 lose visitors before the first paint.

About 541 KiB of JavaScript is downloaded but never used on this page.

Google CDN costs a phone 363 ms of main-thread work and 764 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

A phone's processor spends 2.2 s on main-thread work while loading, 690 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

The page has 1,989 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

4 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and YouTube and others), adding 901 KiB and 402 ms of main-thread time.

5 long tasks block the main thread while loading, the longest for 195 ms. During a long task the page ignores taps.

About 150 KiB of CSS is downloaded but never applied on this page.

Polyfills for old browsers add 11 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

The page becomes fully interactive after 11.0 s. Good is under 3.8 s.

The first text or image appears after 2.9 s on a phone. Good is under 1.8 s.

32 images have no width and height attributes, so the layout jumps as each one loads.

Your largest element takes 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Link Building”.

Visually, the page fills in at 3.6 s (Speed Index). Good is under 3.4 s.

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 4.4 s to 4.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 18.5 MB in 118 requests on a phone: media 15.6 MB (15), images 1.2 MB (76) and scripts 995 KiB (11). Under 2 MB keeps phones on slow connections fast.

Email-Marketing-KPIs-EN-site-768x432.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

10 images (529 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

1 image is downloaded at several times the size a phone draws it, for example robot_1f916-1.png at 256 px wide, shown at 20 px. Resized copies would save about 53 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 5.24 g of CO₂e: 629.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

7 tap targets are too small or too close together to hit reliably with a finger.

2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

122 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 20 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

6 visible links have no text or label, so screen readers cannot say where they go.

4 form fields have no label, so screen readers announce an empty box and autofill guesses.

Your title is 75 characters, so Google will cut it off around 60: “Livepage - Digital Marketing Agency: SEO, PPC, Email Marketing for Business”.

Your meta description is 194 characters; Google truncates after about 160, so the end of your pitch is cut.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 266 pages on livepage.net and 11 external pages.

https://livepage.net/first-step-to-growth declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

https://livepage.net/first-step-to-growth has no meta description, so Google writes the search snippet from whatever text it finds.

https://livepage.net/first-step-to-growth has no <h1> headline, so visitors and search engines get no clear main topic.

https://livepage.net/articles/what-is-lead-generation.html took over 3 s to send its HTML from our server.

We fetched 15 pages linked from your homepage (of 105 found) and read each the way a search engine does.

6 of 29 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Large scripts ship without source maps.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

Your longest form asks for 10 fields (0 required). Every extra field lowers completion.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 961 words of visible text.

Opening the homepage sets 2 cookies, 1 of them by other companies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.