wearehirschfeld.com website review

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

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

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

6 images could be 4.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

6 third-party services load with your homepage (Google Tag Manager, Vimeo and Hubspot and others), adding 15.2 MB and 383 ms of main-thread time.

Vimeo costs a phone 108 ms of main-thread work and 14.8 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.

About 87 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

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

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

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

3 KiB could be saved by minifying JavaScript.

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

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.

Your largest element takes 30.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “BUILT DIFFERENT LEARN MORE”.

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

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 23.5 MB in 123 requests on a phone: other files 14.4 MB (18), images 7.9 MB (23) and scripts 916 KiB (42). Under 2 MB keeps phones on slow connections fast.

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

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

1 link inside paragraphs relies on colour alone to stand out.

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

4 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

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

Your title is 69 characters, so Google will cut it off around 60: “Experiential Marketing Agency | Design, Build & Activate | Hirschfeld”.

Your meta description is 481 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 28 pages on wearehirschfeld.com and 0 external pages.

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

https://wearehirschfeld.com/case-study/cabot-creamery, https://wearehirschfeld.com/case-study/nascar-experience, https://wearehirschfeld.com/case-study/stella-artois, https://wearehirschfeld.com/case-study/heluvagood-dip, https://wearehirschfeld.com/case-study/hellmanns and https://wearehirschfeld.com/case-study/anheuser-busch all use the title “Experiential Marketing Case Studies | Hirschfeld”. Search engines can't tell which page to show for a search, so each competes with the others.

https://wearehirschfeld.com/privacy-policy has no meta description, so Google writes the search snippet from whatever text it finds.

https://wearehirschfeld.com/case-study/cabot-creamery, https://wearehirschfeld.com/case-study/nascar-experience, https://wearehirschfeld.com/case-study/stella-artois, https://wearehirschfeld.com/case-study/heluvagood-dip, https://wearehirschfeld.com/case-study/hellmanns and https://wearehirschfeld.com/case-study/anheuser-busch use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://wearehirschfeld.com/leasable-assets, whose canonical is https://wearehirschfeld.com/leasable-assets-2. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://wearehirschfeld.com/what-we-do, https://wearehirschfeld.com/who-we-are, https://wearehirschfeld.com/case-study/cabot-creamery, https://wearehirschfeld.com/case-study/nascar-experience, https://wearehirschfeld.com/case-study/stella-artois and https://wearehirschfeld.com/case-study/heluvagood-dip and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 11 pages linked from your homepage and read each the way a search engine does.

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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.

Social proof on the homepage: “25+ ACTIVE CLIENTS”. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage has only about 185 words of visible text; thin pages give Google and first-time buyers little to go on.

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

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.

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

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

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.

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