Website review, no card needed

mk.cl logo

mk.cl website review

Visit site (opens in a new tab)Reviewed 18 November 202645 issues · 85 checks

This review found 45 issues worth fixing on mk.cl, 15 of them high impact, across 85 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.8 s3.1 sMay 30Nov 143.8 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.4 s
Jun 6, 20263.2 s
Jun 13, 20263.2 s
Jun 20, 20263.1 s
Jun 27, 20263.2 s
Jul 4, 20263.4 s
Jul 11, 20263.5 s
Jul 18, 20263.6 s
Jul 25, 20263.6 s
Aug 1, 20263.6 s
Aug 8, 20263.5 s
Aug 15, 20263.4 s
Aug 22, 20263.4 s
Aug 29, 20263.5 s
Sep 5, 20263.6 s
Sep 12, 20263.7 s
Sep 19, 20263.7 s
Sep 26, 20263.7 s
Oct 3, 20263.6 s
Oct 10, 20263.6 s
Oct 17, 20263.6 s
Oct 24, 20263.6 s
Oct 31, 20263.6 s
Nov 7, 20263.7 s
Nov 14, 20263.8 s
Real-visitor tap response (INP)75th percentile, phones
243 ms197 msMay 30Nov 14212 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026229 ms
Jun 6, 2026229 ms
Jun 13, 2026228 ms
Jun 20, 2026228 ms
Jun 27, 2026229 ms
Jul 4, 2026232 ms
Jul 11, 2026238 ms
Jul 18, 2026235 ms
Jul 25, 2026232 ms
Aug 1, 2026227 ms
Aug 8, 2026215 ms
Aug 15, 2026209 ms
Aug 22, 2026205 ms
Aug 29, 2026202 ms
Sep 5, 2026205 ms
Sep 12, 2026210 ms
Sep 19, 2026213 ms
Sep 26, 2026220 ms
Oct 3, 2026213 ms
Oct 10, 2026209 ms
Oct 17, 2026208 ms
Oct 24, 2026207 ms
Oct 31, 2026207 ms
Nov 7, 2026212 ms
Nov 14, 2026212 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of mk.cl (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mk.cl at 0.4 s0.4 s
  2. mk.cl at 0.8 s0.8 s
  3. mk.cl at 1.1 s1.1 s
  4. mk.cl at 1.5 s1.5 s
  5. mk.cl at 1.9 s1.9 s
  6. mk.cl at 2.3 s2.3 s
  7. mk.cl at 2.6 s2.6 s
  8. mk.cl at 3.0 s3.0 s

Speed

9 to fix47
  • Reduce unused JavaScript

    3.6 s · 667 KiB

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

  • Mobile performance score: 47

    47/100

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

  • 8 third-party services on the page

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

  • Use efficient cache lifetimes

    950 ms · 383 KiB

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

  • Reduce unused CSS

    750 ms · 154 KiB

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

  • vtexassets.com adds 488 ms

    488 ms

    vtexassets.com costs a phone 488 ms of main-thread work and 1.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 adds 528 ms

    528 ms

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

  • Render-blocking requests

    450 ms

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

  • Main-thread work: 3.1 s

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

  • Legacy JavaScript

    250 ms · 74 KiB

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

  • 10 long tasks on the main thread

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

  • Improve image delivery

    64 KiB

    2 images could be 64 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 22 ms

    22 ms

    Your server sent the HTML in 22 ms, well inside Google's 600 ms guideline.

Core Web Vitals

10 to fix67
  • Fails Core Web Vitals for real visitors

    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.

  • Largest Contentful Paint: 19.7 s

    19.7 s

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

  • Time to Interactive: 19.7 s

    19.7 s

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

  • Speed Index: 10.3 s

    10.3 s

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

  • Real-user CLS: 0.11

    0.11

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

  • Real-user FCP: 2.3 s

    2.3 s

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • Total Blocking Time: 591 ms

    591 ms

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

  • First Contentful Paint: 2.8 s

    2.8 s

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

  • 2 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -7%

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

  • Largest content (LCP) got 13% slower for real visitors

    +13%

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

3 checks passed
  • Real-user LCP: 2.4 s

    2.4 s

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

  • Real-user INP: 189 ms

    189 ms

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

  • Cumulative Layout Shift: 0.006

    0.006

    The layout barely moves while loading (CLS 0.006, good is under 0.1).

Images and page weight

2 to fix81
  • Page weight: 3.1 MB in 148 requests

    3.1 MB

    Your homepage downloads 3.1 MB in 148 requests on a phone: scripts 2.0 MB (66), other files 395 KiB (55) and fonts 297 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    b05a2e6a-ee4e-4f5b-97cf-9b7f91076b9d___9c46ffbe0334b9ea8bed3 is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 1 image in older formats

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

  • About 0.9 g of CO₂ per visit

    0.89 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

8 to fixGoogle 8389
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Hidden but focusable

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

  • Orphan list items

    Some list items are not inside a list.

  • All page content should be contained by landmarks (5 elements)

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

  • No main landmark

    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)

    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.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 3 links without text

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

2 checks passed
  • Every image has alt text

    All 92 images in the HTML carry an alt attribute.

  • 39 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10083
  • No H1 headline

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

  • Structured data has 1 problem

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

  • No social preview image

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

  • No X (Twitter) card tag

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

  • 106 internal links, 2 external

    The homepage links to 106 pages on mk.cl and 2 external pages.

5 checks passed
  • Meta description: 151 characters

    Your meta description is 151 characters: “Soluciones para construir y remodelar tu espacio con el mejor diseño y calidad: pisos, muros, revestimientos y más. Dis…”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “MK Tienda Online: Productos para construir y remodelar”.

  • Canonical URL set

    The canonical URL is https://www.mk.cl/.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.mk.cl/sitemap.xml.

AI search readiness

1 to fix83
  • No Organization structured data

    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.

  • No llms.txt

    There is no https://www.mk.cl/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.

1 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

Other pages

5 to fix67
  • 6 pages without a title

    https://www.mk.cl/pisos-y-muros, https://www.mk.cl/pisos-y-muros/porcelanatos, https://www.mk.cl/pisos-y-muros/ceramicas, https://www.mk.cl/pisos-y-muros/pisos-flotantes, https://www.mk.cl/pisos-y-muros/vinilicos-en-palmeta and https://www.mk.cl/pisos-y-muros/wall-panels have no <title>, so Google invents the link text in results.

  • 3 pages share a title

    /, https://www.mk.cl/sigue-tu-compra and https://www.mk.cl/centro-de-ayuda all use the title “MK Tienda Online: Productos para construir y remodelar”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 6 pages without a meta description

    https://www.mk.cl/pisos-y-muros, https://www.mk.cl/pisos-y-muros/porcelanatos, https://www.mk.cl/pisos-y-muros/ceramicas, https://www.mk.cl/pisos-y-muros/pisos-flotantes, https://www.mk.cl/pisos-y-muros/vinilicos-en-palmeta and https://www.mk.cl/pisos-y-muros/wall-panels have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages share a meta description

    https://www.mk.cl/sigue-tu-compra, https://www.mk.cl/centro-de-ayuda/tiendas, https://www.mk.cl/centro-de-ayuda and https://www.mk.cl/wishlist use the same meta description. A description written for each page earns more clicks.

  • 9 pages without an H1

    https://www.mk.cl/sigue-tu-compra, https://www.mk.cl/centro-de-ayuda, https://www.mk.cl/wishlist, https://www.mk.cl/pisos-y-muros, https://www.mk.cl/pisos-y-muros/porcelanatos and https://www.mk.cl/pisos-y-muros/ceramicas and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 6 pages slow to respond

    https://www.mk.cl/pisos-y-muros, https://www.mk.cl/pisos-y-muros/porcelanatos, https://www.mk.cl/pisos-y-muros/ceramicas, https://www.mk.cl/pisos-y-muros/vinilicos-en-palmeta, https://www.mk.cl/pisos-y-muros/vinilicos-en-rollo and https://www.mk.cl/pisos-y-muros/wall-panels took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

3 to fixGoogle 9671
  • 4 broken images

    4 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=343162867&tm=gtm002&Ver=2&mid=5c961bab-d55c-44a5-8e06-e13f7e2cf874&bo=1&sid=d0f7aa10e2f711f187984df3af4dbcab&vid=d0f7d410e2f711f18ea7ef98549b9f59&vids=1&msclkid=N&gtm_.

  • 17 small tap targets

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

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Cannot destructure property 'store' of '(intermediate value)' as it is undefined.”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix30
  • No call to action on the first screen

    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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No social proof

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

  • Only about 110 words

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

  • Phone number is not tap-to-call

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

  • No form on the homepage

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

  • No risk reducer

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

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager, Meta Pixel and TikTok Pixel.

Privacy and tracking

  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 mores (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

  • 10 cookies set on arrival

    10

    Opening the homepage sets 10 cookies (measured from a US location before any click).

  • 39 other companies contacted

    Loading the homepage contacts 39 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) loads with the page.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at mk.cl, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
React
Analytics
Google Tag Manager
Hosting
As15311 Telefonica Empresas Chile Sa

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 45 issues on mk.cl, including 19 speed issues, 3 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25