greenmarbles.com website review

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

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

8 third-party services load with your homepage (Squarespace, Google Tag Manager and Hubspot and others), adding 3.4 MB and 884 ms of main-thread time.

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

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

Squarespace costs a phone 599 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.

About 542 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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

Polyfills for old browsers add 109 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 page becomes fully interactive after 12.9 s. Good is under 3.8 s.

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

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

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

Your largest element takes 2.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Smart, Safe, & Sustainable Solutions”. Most of its time is element render delay (1.4 s).

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 3.5 MB in 113 requests on a phone: images 1.8 MB (14), scripts 1.4 MB (59) and stylesheets 170 KiB (10). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example home-construction.png at 693 px wide, shown at 183 px. Resized copies would save about 160 KiB.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

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

There are 3 <h1> headlines (“Smart, Safe, & Sustainable Solutions”, “What Makes Us Different?” and “Our Approach To Solution Design Is Simple”). 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/63b759c9272f6855997…”.

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

The homepage links to 46 pages on greenmarbles.com and 0 external pages.

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.

/multi-family-properties and /who-we-help all use the title “Sustainable Solutions For Multi-Family Properties — GreenMarbles - Sm…”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

/corporate-sustainability, /csp, /about and /contact-us have no meta description, so Google writes the search snippet from whatever text it finds.

/multi-family-properties and /who-we-help use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example /who-we-help, whose canonical is /multi-family-properties. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/corporate-sustainability, /about and /contact-us have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://data.stbuttons.click/data' from origin 'https://greenmarbles.com' has been blocked…”.

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

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.

greenmarbles.com is registered until Dec 2026. Make sure auto-renew is on and the card on file is current.

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

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

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

DMARC is set to p=none, so mail pretending to be greenmarbles.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 Analytics, Google Tag Manager and HubSpot (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 10 cookies (measured from a US location before any click).

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