salsabooth.com website review

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, figpii.com and Affirm and others), adding 1.1 MB and 2.4 s of main-thread time.

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

figpii.com costs a phone 540 ms of main-thread work and 93 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 500 ms.

1 image could be 48 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

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

Affirm costs a phone 285 ms of main-thread work and 165 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.

cloudfront.net costs a phone 264 ms of main-thread work and 66 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 97 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

4 KiB could be saved by minifying CSS.

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

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

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

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

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

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

Your homepage downloads 3.3 MB in 282 requests on a phone: scripts 1.6 MB (70), other files 1.1 MB (160) and images 395 KiB (34). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example home-tablet.jpg at 1,600 px wide, shown at 390 px. Resized copies would save about 66 KiB.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

Some lists contain elements other than list items, which screen readers announce wrongly.

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.

The homepage links to 130 pages on salsabooth.com and 22 external pages.

https://photoboothsupplyco.com/pages/pb-quiz-all is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://photoboothsupplyco.com/pages/salsa-2-pricing, https://photoboothsupplyco.com/pages/tortilla-pricing, https://photoboothsupplyco.com/pages/pb-quiz-all, https://photoboothsupplyco.com/pages/fiesta-pricing, https://photoboothsupplyco.com/pages/fiesta-photo-booth-capture and https://photoboothsupplyco.com/pages/fiesta-virtual-booth and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://photoboothsupplyco.com/collections/sale-bundles, https://photoboothsupplyco.com/pages/salsa-2, https://photoboothsupplyco.com/pages/salsa-2-pricing, https://photoboothsupplyco.com/pages/guac-booth, https://photoboothsupplyco.com/pages/guac-packages and https://photoboothsupplyco.com/pages/tortilla and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://photoboothsupplyco.com/pages/fiesta-photo-booth-capture, https://photoboothsupplyco.com/pages/fiesta-virtual-booth, https://photoboothsupplyco.com/pages/fiesta-360, https://photoboothsupplyco.com/pages/fiesta-design-studio and https://photoboothsupplyco.com/pages/fiesta-business-tools took over 3 s to send their HTML from our server.

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

7 of 17 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

6 errors were logged to the browser console while the page loaded, for example “FIGPII is not defined e (https://store-app.figpii.com/script?v=041626&shop=photo-booth-supply-co.myshopify.com:1:591)”.

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

Social proof on the homepage: 111 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.

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 959 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 Meta Pixel and 4 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 41 cookies, 9 of them by other companies (measured from a US location before any click).

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