wexelart.com website review

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

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

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

8 third-party services load with your homepage (JSDelivr CDN, emotivecdn.io and Shopify and others), adding 1.8 MB and 799 ms of main-thread time.

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

About 506 KiB of JavaScript is downloaded but never used on this page.

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

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

Shopify costs a phone 127 ms of main-thread work and 549 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.

emotivecdn.io costs a phone 129 ms of main-thread work and 384 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.

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

Polyfills for old browsers add 76 KiB JavaScript that modern phones do not need.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

4 KiB could be saved by minifying JavaScript.

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

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

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 8.0 MB in 501 requests on a phone: images 4.6 MB (89), scripts 1.8 MB (165) and other files 1.2 MB (213). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example IngridChing_SBX2436-7FICWN_Square_400x.jpg at 390 px wide, shown at 119 px. Resized copies would save about 21 KiB.

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

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

1 element hidden from screen readers can still receive keyboard focus.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is 69 characters, so Google will cut it off around 60: “Acrylic Floating Picture Frames & Art by Emerging Artists | Wexel Art”.

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

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

The homepage links to 175 pages on wexelart.com and 8 external pages.

https://wexelart.com/collections/magnetic-float-frame-wallscapes and https://wexelart.com/collections/wexel-art-gallery have no meta description, so Google writes the search snippet from whatever text it finds.

https://wexelart.com/products/book-stands, https://wexelart.com/products/clear-magnetic-float-frames, https://wexelart.com/products/vinyl-record-picture-frame, https://wexelart.com/products/tt0709-clear-tabletop, https://wexelart.com/products/6-x-6-x-3-modern-acrylic-shadowbox-with-linen-canvas-uv-grade and https://wexelart.com/products/double-panel-15-x-12-wall-frame-dr and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://wexelart.com/collections/shop-frames 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 57 found) and read each the way a search engine does.

3 errors were logged to the browser console while the page loaded, for example “Identifier 'open' has already been declared”.

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.

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

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

The homepage carries about 1,055 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Klaviyo and 3 mores (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 16 cookies, 2 of them by other companies (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 40 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.