anystudios.com website review

323 KiB could be saved by minifying JavaScript.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.4 s.

About 289 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.

8 third-party services load with your homepage (website-files.com, Facebook and Google Tag Manager and others), adding 29.4 MB and 865 ms of main-thread time.

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

Vimeo costs a phone 0 ms of main-thread work and 20.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.

website-files.com costs a phone 482 ms of main-thread work and 8.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 65 (desktop: 81). Pages that score under 90 lose visitors before the first paint.

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

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

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

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

8 KiB could be saved by minifying CSS.

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

Polyfills for old browsers add 12 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 9.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Think fast.”.

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

36 images have no width and height attributes, so the layout jumps as each one loads.

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

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

The layout shifts by 0.102 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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 29.9 MB in 107 requests on a phone: media 20.5 MB (12), images 7.7 MB (63) and scripts 1.0 MB (13). Under 2 MB keeps phones on slow connections fast.

2 images weigh 2.4 MB together. On a phone connection a single image that size takes seconds.

27 images (5.9 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.

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

2 dropdowns have no label.

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

6 form fields have no label, so screen readers announce an empty box and autofill guesses.

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

Your title is only 11 characters: “Any Studios”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 2 <h1> headlines (“Think fast.” and “Certified for Excellence, Built for Performance.”). One clear main headline is easier for people and search engines.

The homepage links to 22 pages on anystudios.com and 8 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 /clients/wiz, /clients/equashield and /clients/buff, which answer with an error. Visitors hit a dead end and search engines drop them.

/work, /studio and /contact use the same meta description. A description written for each page earns more clicks.

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

10 images failed to load on a phone, for example https://www.anystudios.com/.

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

3 links from your homepage to your own site are broken, for example https://www.anystudios.com/clients/wiz (404).

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.

2 links go through two or more redirects, for example http://instagram.com/any.studios.

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.

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

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

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

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 Ads, Google Analytics, Google Tag Manager and Meta Pixel (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 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.