wxystudio.com website review

Your mobile performance score is 74 (desktop: 94). Pages that score under 90 lose visitors before the first paint.

7 images could be 485 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

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

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

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

3 third-party services load with your homepage (JSDelivr CDN, cloudflarestream.com and wxy-labs.org), adding 164 KiB and 19 ms of main-thread time.

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.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 7.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “↓”.

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

Real visitors wait 969 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 77 ms to 81 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

packer.Bw2Qmk35_5oL2o.webp weighs 577 KiB. On a phone connection a single image that size takes seconds.

3 images are downloaded at several times the size a phone draws them, for example packer.Bw2Qmk35_5oL2o.webp at 2,500 px wide, shown at 374 px. Resized copies would save about 706 KiB.

Your homepage downloads 2.5 MB in 94 requests on a phone: images 2.0 MB (13), other files 181 KiB (64) and scripts 144 KiB (9). Under 2 MB keeps phones on slow connections fast.

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

Links must have discernible text: 2 elements on the page fail this check, rated serious by axe-core.

2 tap targets are too small or too close together to hit reliably with a finger.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

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

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

Your meta description is only 35 characters: “A studio for the built environment.”. 70 to 160 characters is enough to sell the click.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

Structured data found (untyped) but with 1 problem, for example “ld+json block 1 is not valid JSON (Expected property name or '}' in JSON at position 5 (line 2 )”.

No XML sitemap at https://www.wxystudio.com/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at wxystudio.com/robots.txt, the first file search crawlers ask for.

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

The homepage links to 30 pages on wxystudio.com and 2 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.wxystudio.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.

Your homepage links to https://www.wxystudio.com/projects/packer_garden_house_facilities_plan, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.wxystudio.com/projects, https://www.wxystudio.com/news, https://www.wxystudio.com/research, https://www.wxystudio.com/about, https://www.wxystudio.com/projects/dsny_manhattan_district_1_2_5_garage_salt_shed and https://www.wxystudio.com/projects/battery_seaglass and 8 others use the same meta description. A description written for each page earns more clicks.

https://www.wxystudio.com/projects, https://www.wxystudio.com/news, https://www.wxystudio.com/research, https://www.wxystudio.com/about, https://www.wxystudio.com/projects/dsny_manhattan_district_1_2_5_garage_salt_shed and https://www.wxystudio.com/projects/battery_seaglass and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.wxystudio.com/news has 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 (of 19 found) and read each the way a search engine does.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Attribution Reporting is deprecated and will be removed. See https://goo.gle/ps-status for details.”).

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

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.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

The homepage shows no opening hours. If customers visit or call, show when.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

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