studiof.com.co website review

14 images could be 3.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.1 s faster on a phone.

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

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

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

About 66 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

Your mobile performance score is 42. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (vtexassets.com, Google Tag Manager and Facebook and others), adding 10.4 MB and 2.1 s of main-thread time.

vtexassets.com costs a phone 856 ms of main-thread work and 9.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.

Google Tag Manager costs a phone 646 ms of main-thread work and 698 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.

Polyfills for old browsers add 57 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.

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

4 KiB could be saved by minifying JavaScript.

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.

For real visitors the layout shifts by 0.64 (75th percentile). Good is under 0.1.

Your largest element takes 29.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Party Season | Studio F”.

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

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

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

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

Real visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 279 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Real visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.

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

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

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

Your homepage downloads 6.3 MB in 138 requests on a phone: images 3.5 MB (33), scripts 2.0 MB (51) and other files 374 KiB (47). Under 2 MB keeps phones on slow connections fast.

9 images are downloaded at several times the size a phone draws them, for example 82498a1b-74a6-4021-85eb-94cbb8add89e___8c5282fecd76e18d64331 at 1,575 px wide, shown at 390 px. Resized copies would save about 2.3 MB.

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

3 images further down the page (336 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image (267 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 1.77 g of CO₂e: 212.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

5 buttons have no accessible name, so screen readers announce just “button”.

ARIA commands must have an accessible name: 8 elements on the page fail this check, rated serious by axe-core.

2 elements hidden from screen readers can still receive keyboard focus.

All page content should be contained by landmarks: 16 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.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Elements with visible text labels do not have matching accessible names. (4 elements).

Structured data found (ItemList and WebSite) but with 1 problem, for example “WebSite: missing name”.

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

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 91 pages on studiof.com.co 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.

There is no https://www.studiof.com.co/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.

https://www.studiof.com.co/ropa/enterizos-y-conjuntos has no <title>, so Google invents the link text in results.

/ and https://www.studiof.com.co/rastreo all use the title “Tienda de ropa | Envíos nacionales | Studio F Colombia”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.studiof.com.co/ropa/enterizos-y-conjuntos has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.studiof.com.co/coleccion/party-season and https://www.studiof.com.co/ropa/enterizos-y-conjuntos have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.studiof.com.co/coleccion/party-season, https://www.studiof.com.co/fall, https://www.studiof.com.co/accesorios/bolsos-y-carteras, https://www.studiof.com.co/ropa/enterizos-y-conjuntos and https://www.studiof.com.co/ropa/ponchos-y-sobretodos took over 3 s to send their HTML from our server.

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

4 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'register')”.

Large scripts ship without source maps.

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.

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

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