420packaging.com website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and Klaviyo and others), adding 1.4 MB and 601 ms of main-thread time.

About 203 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

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

Shopify costs a phone 172 ms of main-thread work and 630 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.

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

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

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

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

3 images could be 33 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

14 KiB could be saved by minifying JavaScript.

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.

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 12.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Assorted cannabis packaging including pre-roll tubes, jars,…”.

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

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

Real visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

Your homepage downloads 3.7 MB in 502 requests on a phone: other files 1.4 MB (271), scripts 1.2 MB (167) and images 663 KiB (41). Under 2 MB keeps phones on slow connections fast.

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

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

37 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.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

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

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

The homepage links to 300 pages on 420packaging.com and 13 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.

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

On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

5 of 21 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 “Uncaught SyntaxError: Identifier 'KountSDKVersion' has already been declared”.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

marijuanapackaging.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

marijuanapackaging.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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.

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

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

The homepage carries about 2,062 words of visible text.

DMARC is set to p=none, so mail pretending to be 420packaging.com is still delivered. Reports are on, so moving to quarantine is the next step.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Klaviyo (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 14 cookies (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 23 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.