birdeye.com website review

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

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

1 file is served with short cache lifetimes, so returning visitors download them again (17 KiB).

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

The layout shifts by 0.43 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

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

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

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

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

Your homepage downloads 9.0 MB in 60 requests on a phone: images 5.8 MB (52), media 3.1 MB (2) and HTML 27 KiB (1). Under 2 MB keeps phones on slow connections fast.

texture-bg.png weighs 1.6 MB. On a phone connection a single image that size takes seconds.

2 images are downloaded at several times the size a phone draws them, for example texture-bg.png at 3,334 px wide, shown at 390 px. Resized copies would save about 1.5 MB.

4 images further down the page (1.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image (58 KiB) is 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.

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

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

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

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

The homepage links to 97 pages on birdeye.com and 23 external pages.

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

/security has no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://id.rlcdn.com/464526.gif.

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

No Content-Security-Policy header, the main browser-side defence against injected scripts.

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

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.

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.

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

There is no form on the homepage, so every lead has to click through to another page first.

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

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 466 words of visible text.

DMARC is set to p=none, so mail pretending to be birdeye.com is still delivered. Add a report address, check the reports, then move to quarantine.

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, Heap and Hotjar and 7 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

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

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