brandedcities.com website review

About 6.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 18.0 s faster on a phone.

85 files are served with short cache lifetimes, so returning visitors download them again (1,000 KiB).

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

10 images could be 389 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.0 s faster on a phone.

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

142 KiB could be saved by minifying JavaScript.

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

6 third-party services load with your homepage (Vimeo, GoDaddy and zi-scripts.com and others), adding 11.3 MB and 861 ms of main-thread time.

Vimeo costs a phone 797 ms of main-thread work and 11.2 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 133 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.

14 KiB could be saved by minifying CSS.

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

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

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 35.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

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

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

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 15.5 MB in 328 requests on a phone: scripts 9.9 MB (109), images 4.5 MB (92) and stylesheets 702 KiB (32). Under 2 MB keeps phones on slow connections fast.

3 images (879 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.

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

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

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

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

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

Your title is 80 characters, so Google will cut it off around 60: “Branded Cities | Getting your brand in front of the audiences you want to reach.”.

There are 6 <h1> headlines (“ICONIC MEDIA. ICONIC DESTINATIONS.”, “We put your brand(s) in front of the audiences yo…” and “Your Brand, Front & Center”). One clear main headline is easier for people and search engines.

The homepage links to 49 pages on brandedcities.com and 3 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.

/markets, /markets/la, /markets/chicago, /markets/philadelphia, /markets/sanfrancisco and /markets/washingtondc and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

/campaignplanning/mappingtool has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 15 pages linked from your homepage (of 24 found) 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.”).

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

Large scripts ship without source maps.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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.

The homepage carries about 526 words of visible text.

Opening the homepage sets 8 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 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.