origlio.com website review

4 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 950 ms faster on a phone.

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

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

4 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.

1 file is served with short cache lifetimes, so returning visitors download them again (111 KiB).

4 third-party services load with your homepage (Google Tag Manager, hcaptcha.com and Google Fonts and others), adding 538 KiB and 229 ms of main-thread time.

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

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

About 12 KiB of CSS is downloaded but never applied on this page.

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 16.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

2 images 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' largest content (lcp) went from 1.3 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.1 MB in 41 requests on a phone: images 3.4 MB (26), scripts 495 KiB (7) and fonts 132 KiB (2). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example white-claw.jpg at 800 px wide, shown at 123 px. Resized copies would save about 58 KiB.

5 images (351 KiB) 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.

4 images further down the page (175 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.16 g of CO₂e: 138.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 elements use ARIA attributes their role does not allow, which confuses screen readers.

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

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

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

The homepage links to 41 pages on origlio.com and 13 external pages.

Your Organization JSON-LD is missing 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 https://www.origlio.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.origlio.com/portfolio, https://www.origlio.com/products/corona, https://www.origlio.com/products/white-claw, https://www.origlio.com/products/yuengling and https://www.origlio.com/products/sierra-nevada are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://www.origlio.com/portfolio, https://www.origlio.com/blog, https://www.origlio.com/products/corona, https://www.origlio.com/products/white-claw, https://www.origlio.com/products/yuengling and https://www.origlio.com/products/sierra-nevada have no meta description, so Google writes the search snippet from whatever text it finds.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“The Protected Audience API is deprecated and will be removed in a future release.”).

Social proof on the homepage: 5 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

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.