uaplimited.com website review

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

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

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

About 768 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 4.5 s faster on a phone.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.9 s).

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

About 1.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

8 third-party services load with your homepage (Intercom, Optanon and Google CDN and others), adding 1.7 MB and 1.1 s of main-thread time.

Intercom costs a phone 725 ms of main-thread work and 968 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.

93 KiB could be saved by minifying CSS.

427 KiB could be saved by minifying JavaScript.

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

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

Google CDN costs a phone 139 ms of main-thread work and 348 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.

Polyfills for old browsers add 18 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

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

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

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

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

Real visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.

Real visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.

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

The layout shifts by 0.141 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

Your homepage downloads 12.5 MB in 103 requests on a phone: images 8.2 MB (40), scripts 3.3 MB (32) and stylesheets 785 KiB (14). Under 2 MB keeps phones on slow connections fast.

homepage-banner-4.png weighs 570 KiB. On a phone connection a single image that size takes seconds.

12 images are downloaded at several times the size a phone draws them, for example homepage-banner-4.png at 1,030 px wide, shown at 342 px. Resized copies would save about 607 KiB.

18 images (1.7 MB) 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.

20 images further down the page (1.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

3 buttons have no accessible name, so screen readers announce just “button”.

Form elements must have labels: 1 element on the page fails this check, rated critical by axe-core.

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

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (1 element).

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 107 characters, so Google will cut it off around 60: “Lock Manufacturers, Door Lock Manufacturer, Hardware Manufacturer, Leading Door Hardware …”.

Structured data found (Corporation and WebSite) but with 1 problem, for example “Corporation: sameAs is an empty list”.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 123 pages on uaplimited.com and 7 external pages.

https://uaplimited.com/resources/type/certificates, https://uaplimited.com/resources/type/brochures, https://uaplimited.com/resources/type/tech-sheets, https://uaplimited.com/resources/type/product-guarantee, https://uaplimited.com/resources/type/maintenance-sheets and https://uaplimited.com/resources/type/booklets and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://uaplimited.com/resources, https://uaplimited.com/careers, https://uaplimited.com/contact-us, https://uaplimited.com/solutions/fire, https://uaplimited.com/solutions/security and https://uaplimited.com/solutions/innovation have no <h1> headline, so visitors and search engines get no clear main topic.

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

3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

1 error was logged to the browser console while the page loaded, for example “initCookieConsent is not defined”.

6 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

Chrome logged issues while loading the page (“Cookie”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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.

The homepage carries about 416 words of visible text.

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

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

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