upserve.com website review

35 files are served with short cache lifetimes, so returning visitors download them again (5.2 MB).

16 images could be 2.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.

About 654 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.

12 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.

Your mobile performance score is 48. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

8 third-party services load with your homepage (Google Tag Manager, posthog.com and Facebook and others), adding 9.6 MB and 1.2 s of main-thread time.

website-files.com costs a phone 104 ms of main-thread work and 8.2 MB 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.

Google Tag Manager costs a phone 443 ms of main-thread work and 522 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.

About 82 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

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

posthog.com costs a phone 256 ms of main-thread work and 251 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.

17 KiB could be saved by minifying CSS.

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

19 KiB JavaScript is shipped twice across bundles.

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.

Your largest element takes 12.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

Scripts block taps and scrolling for 741 ms in total while the page loads. Good is under 200 ms.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 64 ms to 111 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

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

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

Your homepage downloads 9.8 MB in 118 requests on a phone: media 4.8 MB (2), images 3.1 MB (24) and scripts 1.6 MB (50). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example 6aa8f83474da6eb8f100fc27_logo-rodizio-grill.png at 393 px wide, shown at 85 px. Resized copies would save about 30 KiB.

3 images (125 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.

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 10 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.

1 visible link has no text or label, so screen readers cannot say where it goes.

Your title is 66 characters, so Google will cut it off around 60: “Upserve Restaurant Management Software | POS, Payments & Analytics”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 2 <h1> headlines (“Restaurant POS built by restauranteurs” and “Great service starts with great training”). One clear main headline is easier for people and search engines.

Your meta description is 176 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.

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 61 pages on upserve.com and 8 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://www.upserve.com/about-us and https://www.upserve.com/resources use the same meta description. A description written for each page earns more clicks.

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Social proof on the homepage: 7 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

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 522 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (measured from a US location before any click). A consent tool (Usercentrics) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 10 cookies (measured from a US location before any click).

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