premiercomms.com website review

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

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

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

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

3 third-party services load with your homepage (Squarespace, sqspcdn.com and squarespace-cdn.com), adding 5.3 MB and 448 ms of main-thread time.

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

Squarespace costs a phone 431 ms of main-thread work and 1.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.

squarespace-cdn.com costs a phone 0 ms of main-thread work and 4.0 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.

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

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

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

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.

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

Your largest element takes 7.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Select “Accept all” to agree to our use of cookies and simi…”.

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

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

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

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

Your homepage downloads 5.5 MB in 97 requests on a phone: images 3.8 MB (32), scripts 1.1 MB (43) and fonts 239 KiB (7). Under 2 MB keeps phones on slow connections fast.

7 images further down the page (319 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 24 characters: “Premier Public Relations”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 3 <h1> headlines (“About Us”, “SERVICES” and “RECENT WORK”). One clear main headline is easier for people and search engines.

Structured data found (LocalBusiness and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/67195fd828082b5ea47…”.

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

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 43 pages on premiercomms.com and 6 external pages.

A phone browser shows 3,711 words, but the HTML your server sends has only 216. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

Your Organization JSON-LD is missing name, url, logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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.

/home declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and /home all use the title “Premier Public Relations”. Search engines can't tell which page to show for a search, so each competes with the others.

/home, /careers, /art-and-culture, /brands, /charity and /classical-music and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

/careers, /art-and-culture, /brands, /charity, /classical-music and /contemporary-music and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

/corporate, /placemaking and /strategic-consulting have 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 30 found) and read each the way a search engine does.

3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/versioned-site-css/67195fd828082b5ea47a768a/289/5c5…”.

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

HSTS is set, but max-age is 180 days; one year is the recommended minimum.

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

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

premiercomms.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

premiercomms.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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 3,711 words of visible text.

DMARC is set to p=none, so mail pretending to be premiercomms.com is still delivered. Reports are on, so moving to quarantine is the next step.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

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.

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