A free, working cannabis & CBD SEO library, 500 guides. Browse the library ›
Home » Blog » Web Design, UX & Conversion » How to Improve Cannabis Site Speed and UX Together
Web Design, UX & Conversion

How to Improve Cannabis Site Speed and UX Together

In short

Speed is not a separate technical chore from user experience, it is part of the experience. Core Web Vitals are literally UX measurements. Run PageSpeed Insights, fix the image weight that is almost always the culprit, add skeleton loaders so the page feels fast while it loads, and you improve both the numbers and how the site feels in one pass.

Core Web Vitals are UX metrics wearing a technical name

It is easy to file speed under engineering and experience under design, but Google's Core Web Vitals blur that line on purpose. Largest Contentful Paint is how long until the shopper sees the main content. Interaction to Next Paint is how quickly the page responds when they tap. Cumulative Layout Shift is whether things jump around under their finger. Those are all experience questions measured in numbers. Treat the three vitals as your UX scorecard and speed stops being a separate project.

Start by measuring with PageSpeed Insights

Do not guess at speed. Run the page through Google PageSpeed Insights, which gives you a lab score plus, on pages with enough traffic, the real vitals your visitors actually hit. Look at the mobile tab first, because that is where most dispensary traffic lives and where scores drop hardest. The report ranks its own suggestions, so you get a fix list ordered by impact rather than a vague sense that the site feels slow.

Attack image weight first

On a cannabis site the culprit is nearly always the images. A menu is wall-to-wall product photos, and if they ship as full-size JPEGs the page drags megabytes it never needed. Convert to WebP or AVIF, size each file to how it actually displays, and lazy-load anything below the fold. One dispensary menu I looked at was shipping 6 MB of images on the first screen alone; formatting and sizing them cut it to under a megabyte and the mobile LCP dropped below the 2.5-second line without touching anything else. This is the highest-return fix on most sites — it improves both the score and the felt experience at once.

Use skeleton loaders to win on perceived speed

How fast a page feels is not always the same as how fast it loads. A skeleton loader, the grey placeholder blocks in the shape of the content, tells the shopper something is coming and the page is not broken. The milliseconds may be identical, but a page that shows its skeleton and fills in feels faster than a blank white screen that snaps into place. Perceived speed is a real lever, and it is pure experience work that also flatters your vitals.

Mobile is where speed and experience meet hardest

A phone on a mid-strength connection is the harshest test of both. Slow load there is not a small dip, it is the shopper on 4G in a parking lot giving up. Because the mobile audience is the majority and the mobile conditions are the worst, every speed fix you make for mobile is also the experience fix that reaches the most people. Optimize for the phone and the desktop comes along for free.

Keep both in the same review loop

Speed and experience both drift as you add products, banners, and scripts. Rather than a one-time cleanup, put a PageSpeed check and a quick real-device walkthrough on the same recurring schedule, so a new tracking script that tanks INP gets caught the same week it lands. Reviewing them together is less work than chasing them separately, because most of what you find helps both.

Key takeaways

  • Core Web Vitals (LCP, INP, CLS) are UX measurements, so speed and experience are one job.
  • Measure with PageSpeed Insights, mobile tab first, and work its ranked fix list.
  • Image weight is the usual culprit; WebP or AVIF plus sizing and lazy loading is the biggest win.
  • Skeleton loaders improve perceived speed even when raw load time does not change.

Frequently asked questions

What tool should I use to measure cannabis site speed?

Start with Google PageSpeed Insights. It runs a lab test and, when there is enough traffic, shows the real Core Web Vitals your visitors experienced. Check the mobile tab first, because that is where most dispensary traffic is and where scores fall the hardest.

What usually makes a cannabis menu slow?

Image weight, almost every time. Menus are full of product photos, and if they ship as full-size JPEGs the page hauls megabytes it does not need. Converting to WebP or AVIF and sizing files to how they display is usually the single biggest speed win.

What is perceived speed and why does it matter?

Perceived speed is how fast a page feels, which is not always the same as the raw load time. A skeleton loader that shows the shape of the content while it loads makes the wait feel shorter and keeps shoppers from thinking the page is broken, even when the actual milliseconds have not changed.

Want this done for your brand?

We build cannabis & CBD search visibility with full transparency, for dispensaries, brands, and MSOs.

Get a free cannabis SEO audit ›