Website review, no card needed

hollywooddj.com logo

hollywooddj.com website review

Visit site (opens in a new tab)Reviewed 5 November 202634 issues · 91 checks

This review found 34 issues worth fixing on hollywooddj.com, 10 of them high impact, across 91 checks. The most urgent: page weight: 7.0 MB in 424 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.3 s1.6 sMay 16Oct 311.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.1 s
May 23, 20262.1 s
May 30, 20262.0 s
Jun 6, 20262.1 s
Jun 13, 20262.1 s
Jun 20, 20262.2 s
Jun 27, 20262.2 s
Jul 4, 20262.2 s
Jul 11, 20262.2 s
Jul 18, 20262.1 s
Jul 25, 20262.0 s
Aug 1, 20262.0 s
Aug 8, 20261.9 s
Aug 15, 20261.9 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20261.8 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20261.8 s
Oct 3, 20261.8 s
Oct 10, 20261.7 s
Oct 17, 20261.7 s
Oct 24, 20261.7 s
Oct 31, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
209 ms147 msMay 16Oct 31171 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026154 ms
May 23, 2026155 ms
May 30, 2026158 ms
Jun 6, 2026165 ms
Jun 13, 2026168 ms
Jun 20, 2026169 ms
Jun 27, 2026171 ms
Jul 4, 2026163 ms
Jul 11, 2026171 ms
Jul 18, 2026171 ms
Jul 25, 2026171 ms
Aug 1, 2026172 ms
Aug 8, 2026178 ms
Aug 15, 2026187 ms
Aug 22, 2026195 ms
Aug 29, 2026202 ms
Sep 5, 2026191 ms
Sep 12, 2026187 ms
Sep 19, 2026180 ms
Sep 26, 2026172 ms
Oct 3, 2026177 ms
Oct 10, 2026178 ms
Oct 17, 2026174 ms
Oct 24, 2026171 ms
Oct 31, 2026171 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of hollywooddj.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. hollywooddj.com at 0.9 s0.9 s
  2. hollywooddj.com at 1.9 s1.9 s
  3. hollywooddj.com at 2.8 s2.8 s
  4. hollywooddj.com at 3.8 s3.8 s
  5. hollywooddj.com at 4.7 s4.7 s
  6. hollywooddj.com at 5.7 s5.7 s
  7. hollywooddj.com at 6.6 s6.6 s
  8. hollywooddj.com at 7.6 s7.6 s

Speed

10 to fix61
  • Main-thread work: 5.4 s

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

  • 5,370 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, loox.io and rebuyengine.com and others), adding 3.0 MB and 1.4 s of main-thread time.

  • Reduce unused JavaScript

    1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page.

  • Mobile performance score: 61

    61/100

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

  • Shopify adds 794 ms

    794 ms

    Shopify costs a phone 794 ms of main-thread work and 1.9 MB 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.

  • Improve image delivery

    100 ms · 694 KiB

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

  • Use efficient cache lifetimes

    300 ms · 291 KiB

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

  • loox.io adds 256 ms

    256 ms

    loox.io costs a phone 256 ms of main-thread work and 178 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.

  • rebuyengine.com adds 152 ms

    152 ms

    rebuyengine.com costs a phone 152 ms of main-thread work and 501 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.

  • Reduce unused CSS

    150 ms · 171 KiB

    About 171 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.

  • Minify JavaScript

    150 ms · 51 KiB

    51 KiB could be saved by minifying JavaScript.

  • 9 long tasks on the main thread

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

  • Minify CSS

    150 ms · 22 KiB

    22 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    67 KiB

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

  • Font display

    50 ms

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

  • Chained critical requests

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 17 ms

    17 ms

    Your server sent the HTML in 17 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix100
  • Time to Interactive: 32.5 s

    32.5 s

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

  • Speed Index: 9.0 s

    9.0 s

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

  • Largest Contentful Paint: 5.4 s

    5.4 s

    Your largest element takes 5.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “In stock and ready to ship: Technics SL-1200M7G-H 55th Anni…”.

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • Total Blocking Time: 334 ms

    334 ms

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

  • 2 images without width and height

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

  • Tap response (INP) got 11% slower for real visitors

    +11%

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

8 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 1.7 s

    1.7 s

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

  • Real-user INP: 171 ms

    171 ms

    Real visitors wait 171 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 637 ms

    637 ms

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

  • Largest content (LCP) got 20% faster for real visitors

    -20%

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

2 to fix64
  • Page weight: 7.0 MB in 424 requests

    7.0 MB

    Your homepage downloads 7.0 MB in 424 requests on a phone: scripts 2.8 MB (159), other files 2.0 MB (180) and images 1.7 MB (51). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    hdj-jmaz-firestorm-giveaway-mobile-1086x1448.webp 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).

  • 4 images in older formats

    4 images (327 KiB) 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.

  • About 2.0 g of CO₂ per visit

    1.99 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

7 to fixGoogle 8892
  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • 2 images without alt text

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

  • All page content should be contained by landmarks (2 elements)

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

  • Zoom is disabled

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

  • Alternative text of images should not be repeated as text (22 elements)

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

  • 1 link without text

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

  • Headings skip levels

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

1 checks passed
  • 54 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 54 passed and 6 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9293
  • 2 H1 headlines

    There are 2 <h1> headlines (“Hollywood DJ” and “Your Go-To DJ Equipment Source”). One clear main headline is easier for people and search engines.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 647 internal links, 9 external

    The homepage links to 647 pages on hollywooddj.com and 9 external pages.

7 checks passed
  • Meta description: 119 characters

    Your meta description is 119 characters: “DJ Lighting Equipment, Pro Audio, Staging and Truss for sale online. Visit our warehouse in Los Angeles, CA for pickup.”.

  • Title: 35 characters

    Your title is a healthy 35 characters: “Hollywood DJ | DJ Equipment at 100%”.

  • Canonical URL set

    The canonical URL is https://hollywooddj.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, Store and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://hollywooddj.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://hollywooddj.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (3,768 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 1 page without a meta description

    https://hollywooddj.com/pages/contact-us has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://hollywooddj.com/pages/contact-us, whose canonical is https://hollywooddj.com/pages/help-center. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    12 pages of 15 loaded without an error (the rest turned automated requests away).

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 12 pages that loaded have a <title>.

Best practices

4 to fixGoogle 7770
  • 2 broken images

    2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=73004110&Ver=2&mid=9f7146f6-a743-4c7d-b63e-2337254b31fd&bo=3&sid=291494c0d95311f18e4433e7877d63aa&vid=2914c970d95311f19e46916dc72bffbf&vids=0&msclkid=N&pi=918639831&lg.

  • 14 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Shopify's Google Analytics stub called with: [array Array] See https://help.shopify.com/manual/promoting-marketing/pixe…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No map or directions link

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

  • About 1,278 words of copy

    The homepage carries about 1,278 words of visible text.

9 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn more” and “Sign up — it takes a minute”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “Custom Lighting Install Quote”, “Shop our products” and “Shop All DJ Controllers”.

  • 7 short forms

    7 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 22 testimonial or review blocks and 4 trust badges.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Klaviyo and 4 mores (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.

  • 35 cookies set on arrival

    35

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

  • No consent tool detected

    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.

  • 54 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at hollywooddj.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 23 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Blockify Fraud Filter · Pandectes Gdpr · Rebuy Personalization Engine · Uppromote Affiliate · Yotpo Loyalty Rewards · Superspeed Web Vitals · Klaviyo Email Marketing Sms · Region Restrictions · Gdpr Cookie Consent · Affliate By Secomapp · Upsell Koala Discount · Countdown Timer · Swym Wishlist Plus · Smart Menu · Hdj Local Stock And Bins · Surebright Extended Warranty · loox.io · gorgias.chat · cloudfront.net · signifyd.com · 9gtb.com · rebuyengine.com · hubapi.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Cloudflare

Company

Headquarters
Los Angeles

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on hollywooddj.com, including 16 speed issues and 2 SEO issues. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25