peacockconstruction.com website review

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

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

8 third-party services load with your homepage (Squarespace, userway.org and Google CDN and others), adding 5.6 MB and 662 ms of main-thread time.

Your mobile performance score is 52 (desktop: 67). Pages that score under 90 lose visitors before the first paint.

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

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

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

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

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

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

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

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 15.1 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…”.

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

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

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

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

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

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 5.8 MB in 121 requests on a phone: images 4.0 MB (24), scripts 1.2 MB (63) and stylesheets 179 KiB (15). Under 2 MB keeps phones on slow connections fast.

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

3 images are downloaded at several times the size a phone draws them, for example BMP-HDR-Oakland-Childrens-Hospital-Aerials_008+2.jpeg at 1,179 px wide, shown at 343 px. Resized copies would save about 272 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 1.63 g of CO₂e: 196.0 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.

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

Your title is only 20 characters: “Peacock Construction”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 3 <h1> headlines (“Partnerships. Solutions. Solid.”, “Expertise” and “FEATURED PROJECTS”). One clear main headline is easier for people and search engines.

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

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

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

The homepage links to 145 pages on peacockconstruction.com and 3 external pages.

Your Organization JSON-LD is missing name, url, logo and description. 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 https://www.peacockconstruction.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://www.peacockconstruction.com/home, https://www.peacockconstruction.com/about and https://www.peacockconstruction.com/f9b73726-091d-4cc4-a797-61d3aec1c713 declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

/, https://www.peacockconstruction.com/home, https://www.peacockconstruction.com/about and https://www.peacockconstruction.com/f9b73726-091d-4cc4-a797-61d3aec1c713 all use the title “Peacock Construction”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.peacockconstruction.com/portfolio/ariat, https://www.peacockconstruction.com/portfolio/ucsf-benioff-childrens-hospital, https://www.peacockconstruction.com/portfolio/5568-gibraltar-pleasanton, https://www.peacockconstruction.com/portfolio/555-12th-street, https://www.peacockconstruction.com/portfolio/infusion-treatment-center and https://www.peacockconstruction.com/portfolio/33-montgomery-amenity-suite-sj8jn and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.peacockconstruction.com/home, https://www.peacockconstruction.com/about and https://www.peacockconstruction.com/f9b73726-091d-4cc4-a797-61d3aec1c713 use the same meta description. A description written for each page earns more clicks.

https://www.peacockconstruction.com/careers and https://www.peacockconstruction.com/contact-us have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.peacockconstruction.com/careers and https://www.peacockconstruction.com/contact-us 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 25 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/61f80425148a32365551495c/220/5c5…”.

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.

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 1,879 words of visible text.

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