envelopes.sg website review

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

Your mobile performance score is 79. Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (Clarity, Google Tag Manager and Hubspot and others), adding 709 KiB and 771 ms of main-thread time.

3 images could be 74 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

Clarity costs a phone 369 ms of main-thread work and 30 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.

7 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.

16 files are served with short cache lifetimes, so returning visitors download them again (222 KiB).

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

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

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

Polyfills for old browsers add 14 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.

5 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

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

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

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

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

Your homepage downloads 2.6 MB in 399 requests on a phone: other files 1.3 MB (259), scripts 738 KiB (64) and images 290 KiB (53). Under 2 MB keeps phones on slow connections fast.

Crinkle-Paper-Homepage-Banner-Mobile-2.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).

1 image is downloaded at several times the size a phone draws it, for example Lempac_Logo_Singapore.png at 2,260 px wide, shown at 184 px. Resized copies would save about 49 KiB.

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

1 button has no accessible name, so screen readers announce just “button”.

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

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: 4 elements on the page fail this check, rated moderate by axe-core.

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

Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

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

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

The homepage links to 168 pages on envelopes.sg and 4 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://www.lempac.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://www.lempac.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.lempac.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.lempac.com/customer_authentication/redirect and https://www.lempac.com/en-sg/products/glassine-envelopes have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'nextElementSibling')”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

The homepage carries about 770 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Microsoft Clarity (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 29 cookies, 9 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 39 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.