3owl.agency website review

7 images could be 14.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 68.7 s faster on a phone.

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

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

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

3 third-party services load with your homepage (Google Tag Manager, Google Fonts and Google Analytics), adding 230 KiB and 188 ms of main-thread time.

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

About 13 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 60 ms faster on a phone.

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.

2 KiB could be saved by minifying CSS.

Your largest element takes 73.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “22% Lift in SSS”.

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

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

The first text or image appears after 2.6 s on a phone. Good is under 1.8 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 14.9 MB in 79 requests on a phone: images 14.4 MB (19), scripts 344 KiB (26) and stylesheets 73 KiB (31). Under 2 MB keeps phones on slow connections fast.

1 image (127 KiB) is 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.

1 image further down the page (47 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.

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

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

Your title is 67 characters, so Google will cut it off around 60: “Restaurant Web Design & Digital Growth for Multi-Unit Brands | 3Owl”.

The homepage links to 62 pages on 3owl.agency and 0 external pages.

/connect/roi-calculator, /case-study/great-american-cookies-custom-frontend-website, /case-study/willies-icehouse-website-redesign and /case-study/duck-donuts-custom-frontend have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /connect/roi-calculator, whose canonical is /roi-calculator. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/about and /connect/project-inquiry have no <h1> headline, so visitors and search engines get no clear main topic.

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

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

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.

3owl.agency 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.

3owl.agency'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.

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: 7 customer or partner logos. 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.

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

DMARC is set to p=none, so mail pretending to be 3owl.agency is still delivered. Reports are on, so moving to quarantine is the next step.

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