golo.dev website review

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

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

About 175 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

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

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

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

Shopify costs a phone 18 ms of main-thread work and 332 KiB 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.

8 third-party services load with your homepage (cookiepro.com, applovin.com and Shopify and others), adding 655 KiB and 258 ms of main-thread time.

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

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

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

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

Your largest element takes 5.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “More than 5 million people have chosen GOLO to lose weight.…”.

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

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

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

3 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 2.6 MB in 357 requests on a phone: other files 1.6 MB (278), scripts 642 KiB (56) and fonts 164 KiB (3). Under 2 MB keeps phones on slow connections fast.

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

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

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

1 visible link has no text or label, so screen readers cannot say where it goes.

ARIA role should be appropriate for the element: 7 elements on the page fail this check, rated minor by axe-core.

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

Elements with visible text labels do not have matching accessible names. (2 elements).

Structured data found (untyped) but with 1 problem, for example “ld+json block 1 is not valid JSON (Unexpected token ',', ..."@graph": [,] } " is not valid JS)”.

7 links have no real href, so search engines can't follow them.

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 74 pages on golo.dev and 16 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.

Your homepage links to /pages/why-golo, /products/golo-for-life-plan-extended, /products/golo-for-life-plan-members, /pages/mygolo-intro, /pages/mygolo-home-myg1 and /pages/mygolo-wellness-dashboard and 3 others, which answer with an error. Visitors hit a dead end and search engines drop them.

/pages/welcome-to-mygolo-myg1 and /pages/overcoming-diet-obstacles-myg1 are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/pages/golo-foods, /pages/about-us, /pages/welcome-to-mygolo-myg1, /pages/overcoming-diet-obstacles-myg1 and /pages/meal-plans use the same meta description. A description written for each page earns more clicks.

/pages/about-us has no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 29 found) and read each the way a search engine does.

10 images failed to load on a phone, for example https://golo.dev/.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

12 links from your homepage to your own site are broken, for example https://golo.dev/pages/why-golo (404).

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

3 links go through two or more redirects, for example https://golo.dev/customer_authentication/login?return_to=%2F&locale=en&ui_hint=full&region_country=US.

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.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

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

golo.dev 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.

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.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

The homepage carries about 2,816 words of visible text.

DMARC is set to p=none, so mail pretending to be golo.dev 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.

Before a visitor clicks anything, the page loads Google Tag Manager and Klaviyo (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

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

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