justingenovese.com website review

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

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

4 third-party services load with your homepage (Squarespace, sqspcdn.com and JSDelivr CDN and others), adding 30.5 MB and 701 ms of main-thread time.

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

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

Squarespace costs a phone 696 ms of main-thread work and 2.7 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 137 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.

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

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

Polyfills for old browsers add 34 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.

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

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

Visually, the page fills in at 8.6 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.

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 “I'm a brand-building-creative-directing-team-empowering-sus…”. Most of its time is element render delay (2.5 s).

14 images 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 30.6 MB in 62 requests on a phone: images 29.4 MB (14), scripts 954 KiB (23) and stylesheets 166 KiB (9). Under 2 MB keeps phones on slow connections fast.

3 images weigh 25.8 MB together. On a phone connection a single image that size takes seconds.

4 images are downloaded at several times the size a phone draws them, for example Port-Thumb-Waternative-1.gif at 1,260 px wide, shown at 326 px. Resized copies would save about 12.6 MB.

3 images further down the page (25.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

2 images (25.3 MB) 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 8.67 g of CO₂e: 1040.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

14 images have no alt text, which hurts accessibility and image search.

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

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 15 characters: “Justin Genovese”. Between 30 and 65 characters leaves room to say what you do and for whom.

No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 38 pages on justingenovese.com and 0 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://www.justingenovese.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.justingenovese.com/about, https://www.justingenovese.com/ringcentral-smb, https://www.justingenovese.com/ringcentral-brandsystem, https://www.justingenovese.com/ringcentral-impactreport, https://www.justingenovese.com/mangomint-brand and https://www.justingenovese.com/mangomint-product and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.justingenovese.com/about, https://www.justingenovese.com/ringcentral-smb, https://www.justingenovese.com/ringcentral-brandsystem, https://www.justingenovese.com/ringcentral-impactreport, https://www.justingenovese.com/mangomint-brand and https://www.justingenovese.com/mangomint-product and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.justingenovese.com/ringcentral-smb, https://www.justingenovese.com/ringcentral-impactreport, https://www.justingenovese.com/mangomint-gotomarket and https://www.justingenovese.com/nissan 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 and read each the way a search engine does.

5 of 12 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 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/5ebd8ea7e3bec926459765a4/232/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.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

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

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

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Opening the homepage sets 3 cookies (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.