Website review, no card needed

bright.com logo

bright.com website review

Visit site (opens in a new tab)Reviewed 20 November 202649 issues · 98 checks

This review found 49 issues worth fixing on bright.com, 18 of them high impact, across 98 checks. The most urgent: use efficient cache lifetimes. 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.7 s1.3 sMay 30Nov 142.5 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.5 s
Jun 6, 20261.5 s
Jun 13, 20261.5 s
Jun 20, 20261.6 s
Jun 27, 20261.5 s
Jul 4, 20261.5 s
Jul 11, 20261.5 s
Jul 18, 20261.5 s
Jul 25, 20261.6 s
Aug 1, 20261.6 s
Aug 8, 20261.6 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.7 s
Sep 5, 20261.6 s
Sep 12, 20261.6 s
Sep 19, 20261.6 s
Sep 26, 20261.6 s
Oct 3, 20261.6 s
Oct 10, 20261.7 s
Oct 17, 20261.9 s
Oct 24, 20262.2 s
Oct 31, 20262.4 s
Nov 7, 20262.6 s
Nov 14, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
86 ms59 msMay 30Nov 1472 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202662 ms
Jun 6, 202662 ms
Jun 13, 202663 ms
Jun 20, 202663 ms
Jun 27, 202664 ms
Jul 4, 202664 ms
Jul 11, 202662 ms
Jul 18, 202662 ms
Jul 25, 202663 ms
Aug 1, 202665 ms
Aug 8, 202668 ms
Aug 15, 202669 ms
Aug 22, 202668 ms
Aug 29, 202670 ms
Sep 5, 202671 ms
Sep 12, 202678 ms
Sep 19, 202679 ms
Sep 26, 202680 ms
Oct 3, 202681 ms
Oct 10, 202679 ms
Oct 17, 202683 ms
Oct 24, 202678 ms
Oct 31, 202677 ms
Nov 7, 202677 ms
Nov 14, 202672 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 bright.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. bright.com at 0.4 s0.4 s
  2. bright.com at 0.8 s0.8 s
  3. bright.com at 1.1 s1.1 s
  4. bright.com at 1.5 s1.5 s
  5. bright.com at 1.9 s1.9 s
  6. bright.com at 2.3 s2.3 s
  7. bright.com at 2.6 s2.6 s
  8. bright.com at 3.0 s3.0 s

Speed

10 to fix57
  • Use efficient cache lifetimes

    2.7 s · 38.5 MB

    68 files are served with short cache lifetimes, so returning visitors download them again (38.5 MB).

  • Improve image delivery

    1.5 s · 7.9 MB

    12 images could be 7.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.5 s faster on a phone.

  • Render-blocking requests

    2.8 s

    25 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.8 s.

  • Google CDN adds 1.0 s

    1.0 s

    Google CDN costs a phone 1.0 s of main-thread work and 1.1 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and Google Maps and others), adding 1.4 MB and 1.3 s of main-thread time.

  • Reduce unused JavaScript

    450 ms · 756 KiB

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

  • Mobile performance score: 57

    57/100

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

  • Main-thread work: 3.3 s

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

  • 13 long tasks on the main thread

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

  • 1,503 HTML elements

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

  • Reduce unused CSS

    150 ms · 35 KiB

    About 35 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 CSS

    13 KiB

    13 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    11 KiB

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

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 36 ms

    36 ms

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

Core Web Vitals

12 to fix67
  • Fails Core Web Vitals for real visitors

    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.

  • Time to Interactive: 14.1 s

    14.1 s

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

  • Largest Contentful Paint: 5.3 s

    5.3 s

    Your largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Bright Event Rentals Slide”.

  • Total Blocking Time: 681 ms

    681 ms

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

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • Real-user LCP: 2.8 s

    2.8 s

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

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

    +20%

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

  • Largest content (LCP) got 68% slower for real visitors

    +68%

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • Speed Index: 3.6 s

    3.6 s

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

  • 10 images without width and height

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

3 checks passed
  • Real-user INP: 88 ms

    88 ms

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

  • Real-user CLS: 0.02

    0.02

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

  • Cumulative Layout Shift: 0.02

    0.02

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

Images and page weight

5 to fix14
  • Page weight: 40.2 MB in 104 requests

    40.2 MB

    Your homepage downloads 40.2 MB in 104 requests on a phone: media 26.5 MB (2), images 11.8 MB (46) and scripts 1.3 MB (22). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 3.2 MB together. On a phone connection a single image that size takes seconds.

  • 3 images far larger than shown

    572 KiB

    3 images are downloaded at several times the size a phone draws them, for example 4-2026_CA-PHX_Banner_One-Rental-Partner-1.png at 1,600 px wide, shown at 390 px. Resized copies would save about 572 KiB.

  • 6 images in older formats

    6 images (4.5 MB) 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.

  • An image on the first screen is lazy-loaded

    4-2026_CA-PHX_Banner_One-Rental-Partner-1.png 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).

  • About 11.4 g of CO₂ per visit

    11.39 g

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

Accessibility

12 to fixGoogle 7680
  • 6 buttons without a name

    6 buttons have no accessible name, so screen readers announce just “button”.

  • Image buttons must have alternative text (1 element)

    Image buttons must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

  • 28 text elements with low contrast

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

  • 16 tap targets too small

    16 tap targets are too small or too close together to hit reliably with a finger.

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 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 (44 elements)

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 4 links without text

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

  • Elements use prohibited ARIA attributes

    Elements use prohibited ARIA attributes (1 element).

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Headings skip levels

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

1 checks passed
  • 34 automated accessibility rules passed

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

SEO

4 to fixGoogle 9288
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 5 H1 headlines

    There are 5 <h1> headlines (“Curated Event Rentals Across Northern California …”, “One Rental Partner. Endless Possibilities.” and “Sacramento, Your Events Just Got Brighter”). One clear main headline is easier for people and search engines.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 236 internal links, 7 external

    The homepage links to 236 pages on bright.com and 7 external pages.

6 checks passed
  • Meta description: 121 characters

    Your meta description is 121 characters: “Experienced event professionals completely dedicated to ensuring you and your guests have an incredible, indelible even…”.

  • Title: 48 characters

    Your title is a healthy 48 characters: “Bright Rentals | Event Rentals for Professionals”.

  • Canonical URL set

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

  • 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://bright.com/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://bright.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.

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

  • Text is in the HTML

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

Other pages

1 to fix95
  • 13 pages without a meta description

    https://bright.com/locations/los-angeles, https://bright.com/locations/thousand-oaks, https://bright.com/locations/palm-springs, https://bright.com/locations/san-diego, https://bright.com/locations/orange-county and https://bright.com/locations/santa-barbara and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • 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 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 8586
  • Scrolls sideways on phones

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 2 low-resolution images

    2 images are served at too low a resolution for sharp phone screens.

  • Requests the geolocation permission on page load

    Requests the geolocation permission on page load.

2 checks passed
  • Tap targets are thumb-sized

    25 of 29 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix86
  • Local business without LocalBusiness data

    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.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

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

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 735 words of copy

    The homepage carries about 735 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop All” and “Shop What's New”.

  • 19 calls to action

    The homepage has 19 calls to action, for example “Sign In / Register”, “Shop the Look” and “Download the Bright App”.

  • 2 short forms

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

  • Social proof on the page

    Social proof on the homepage: 40 testimonial or review blocks, 1 customer or partner logo, a star rating and “7000+ customers”.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 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.

  • 11 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 bright.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Hosting
CoreSpace, Inc.

Hiring

Hiring
42 open roles
Teams
Warehouse (1)
Job board
paylocity

Company

Founded
2011
Headquarters
San Francisco

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 49 issues on bright.com, including 22 speed issues, 4 SEO issues and 2 conversion gaps. 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