jessicabara.com website review

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

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

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

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

8 third-party services load with your homepage (Shopify, POWr and Klaviyo and others), adding 1.4 MB and 762 ms of main-thread time.

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

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

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

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

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

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

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

27 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 25 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.

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

3 KiB JavaScript is shipped twice across bundles.

2 KiB could be saved by minifying CSS.

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

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

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

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

Your homepage downloads 9.2 MB in 403 requests on a phone: media 4.5 MB (1), images 2.0 MB (42) and scripts 1.2 MB (162). Under 2 MB keeps phones on slow connections fast.

1 image (91 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.

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

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

1 image has no alt text, which hurts accessibility and image search.

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

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

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

Your title is only 27 characters: “Jessica Bara – JESSICA BARA”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

Your <h1> is empty.

The homepage links to 210 pages on jessicabara.com and 13 external pages.

https://www.jessicabara.com/collections/all-dresses-1, https://www.jessicabara.com/collections/accessories-1, https://www.jessicabara.com/collections/anet-mlcakova, https://www.jessicabara.com/collections/arina-nazarova, https://www.jessicabara.com/collections/aleska-genesis and https://www.jessicabara.com/collections/alexa-collins and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

2 errors were logged to the browser console while the page loaded, for example “AbortError: The play() request was interrupted by a call to pause(). https://goo.gl/LdLk22”.

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.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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.

The homepage carries about 456 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo, Meta Pixel and Pinterest Tag and 1 more (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 22 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 31 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.