runningskirts.com website review

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

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

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

8 third-party services load with your homepage (Bold Commerce, Klaviyo and SocialShopWave and others), adding 1.5 MB and 748 ms of main-thread time.

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

Bold Commerce costs a phone 313 ms of main-thread work and 485 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 335 ms. During a long task the page ignores taps.

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

Klaviyo costs a phone 159 ms of main-thread work and 319 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.

LoyaltyLion costs a phone 40 ms of main-thread work and 345 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.

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

Polyfills for old browsers add 45 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 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.

Your largest element takes 16.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “DIFFICULT BUSINESS UPDATE”.

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 76 ms to 94 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 0.8 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Scripts block taps and scrolling for 320 ms in total while the page loads. Good is under 200 ms.

17 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 4.1 MB in 292 requests on a phone: scripts 1.5 MB (107), images 1.4 MB (30) and other files 902 KiB (135). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example as-bubblegum-houndstooth_b0808159-710d-4325-b14c-d2e85885ef9 at 500 px wide, shown at 162 px. Resized copies would save about 7 KiB.

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

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

Interactive controls must not be nested: 4 elements on the page fail this check, rated serious by axe-core.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

Your title is 85 characters, so Google will cut it off around 60: “Runningskirts Official Website Skirts, Skorts or Shorts Try a Running – RunningSkirts”.

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

1 link has no real href, so search engines can't follow it.

Your <h1> is empty.

The homepage links to 125 pages on runningskirts.com and 5 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.

https://runningskirts.com/collections/mini-dots-polka-dot-prints, https://runningskirts.com/collections/nyc-collection/nyc, https://runningskirts.com/collections/running-costumes and https://runningskirts.com/collections/new-solid-colors 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 https://runningskirts.com/collections/nyc-collection/nyc, whose canonical is https://runningskirts.com/collections/nyc-collection. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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