Tools & Wizards About Us
yamaki.com.co screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

yamaki.com.co

Yamaki | Distribuidores Audio y Sonido profesional, Vídeo e Iluminación

Page Load Speed

8.9 sec in total

First Response

106 ms

Resources Loaded

8.4 sec

Page Rendered

426 ms

yamaki.com.co screenshot

About Website

Visit yamaki.com.co now to see the best up-to-date Yamaki content for Colombia and also check out these interesting facts you probably never knew about yamaki.com.co

Distribuidores Audio y Sonido Profesional, contamos con soluciones especializadas de Música y Audio de Consumo, Sistemas Integrados e Iluminación Profesional.

Visit yamaki.com.co

Key Findings

We analyzed Yamaki.com.co page load time and found that the first response time was 106 ms and then it took 8.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

yamaki.com.co performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value9.9 s

0/100

25%

SI (Speed Index)

Value19.5 s

0/100

10%

TBT (Total Blocking Time)

Value2,100 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.018

100/100

15%

TTI (Time to Interactive)

Value15.7 s

6/100

10%

Network Requests Diagram

yamaki.com.co

106 ms

www.yamaki.com.co

184 ms

js

90 ms

swiper.min.css

129 ms

tippy.css

114 ms

Our browser made a total of 122 requests to load all elements on the main page. We found that 91% of them (111 requests) were addressed to the original Yamaki.com.co, 2% (3 requests) were made to Googletagmanager.com and 2% (3 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (5.2 sec) belongs to the original domain Yamaki.com.co.

Page Optimization Overview & Recommendations

Page size can be reduced by 188.1 kB (11%)

Content Size

1.6 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yamaki.com.co main page is 1.6 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 112.8 kB

  • Original 149.2 kB
  • After minification 141.7 kB
  • After compression 36.3 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 112.8 kB or 76% of the original size.

Image Optimization

-6%

Potential reduce by 65.8 kB

  • Original 1.1 MB
  • After minification 998.3 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Yamaki images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.4 kB

  • Original 282.5 kB
  • After minification 282.5 kB
  • After compression 281.1 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

CSS Optimization

-5%

Potential reduce by 8.1 kB

  • Original 149.4 kB
  • After minification 145.4 kB
  • After compression 141.4 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Yamaki.com.co has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 68 (60%)

Requests Now

114

After Optimization

46

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 114 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yamaki. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 30 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

yamaki.com.co

yamaki.com.co

106 ms

www.yamaki.com.co

www.yamaki.com.co

184 ms

js

js

90 ms

swiper.min.css

swiper.min.css

129 ms

tippy.css

tippy.css

114 ms

gs-logo.min.css

gs-logo.min.css

115 ms

xoo-aff-style.css

xoo-aff-style.css

909 ms

all.min.css

all.min.css

121 ms

select2.css

select2.css

119 ms

chaty-front.min.css

chaty-front.min.css

1905 ms

xoo-el-style.css

xoo-el-style.css

1908 ms

xoo-el-fonts.css

xoo-el-fonts.css

2921 ms

if-menu-site.css

if-menu-site.css

2920 ms

bootstrap.min.css

bootstrap.min.css

2913 ms

css2

css2

57 ms

style.css

style.css

2910 ms

header-logolb.css

header-logolb.css

3918 ms

cherry-handler-styles.min.css

cherry-handler-styles.min.css

3915 ms

jet-widgets.css

jet-widgets.css

3919 ms

jet-widgets-skin.css

jet-widgets-skin.css

3916 ms

juxtapose.css

juxtapose.css

3908 ms

elementor-icons.min.css

elementor-icons.min.css

3897 ms

frontend.min.css

frontend.min.css

3985 ms

swiper.min.css

swiper.min.css

4905 ms

post-13.css

post-13.css

4835 ms

frontend.min.css

frontend.min.css

4095 ms

frontend.min.css

frontend.min.css

4866 ms

global.css

global.css

4901 ms

post-16.css

post-16.css

4909 ms

css

css

41 ms

fontawesome.min.css

fontawesome.min.css

4905 ms

brands.min.css

brands.min.css

4921 ms

jquery.min.js

jquery.min.js

5019 ms

jquery-migrate.min.js

jquery-migrate.min.js

4985 ms

select2.js

select2.js

4988 ms

xoo-aff-js.js

xoo-aff-js.js

4988 ms

frontend-gtag.min.js

frontend-gtag.min.js

5014 ms

my_custom_script.js

my_custom_script.js

5012 ms

js

js

56 ms

animations.min.css

animations.min.css

5143 ms

swiper.min.js

swiper.min.js

5150 ms

TweenMax.min.js

TweenMax.min.js

32 ms

ScrollMagic.js

ScrollMagic.js

43 ms

animation.gsap.js

animation.gsap.js

53 ms

tippy-bundle.umd.min.js

tippy-bundle.umd.min.js

5138 ms

images-loaded.min.js

images-loaded.min.js

5062 ms

gs-logo.min.js

gs-logo.min.js

5061 ms

cherry-js-core.min.js

cherry-js-core.min.js

5057 ms

xoo-el-js.js

xoo-el-js.js

5071 ms

cht-front-script.min.js

cht-front-script.min.js

5068 ms

navigation.js

navigation.js

4286 ms

bootstrap.min.js

bootstrap.min.js

3323 ms

global.js

global.js

3322 ms

cherry-handler.min.js

cherry-handler.min.js

2658 ms

tooltipster.min.js

tooltipster.min.js

3017 ms

frontend-buttons.min.js

frontend-buttons.min.js

3019 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

3012 ms

webpack.runtime.min.js

webpack.runtime.min.js

2019 ms

frontend-modules.min.js

frontend-modules.min.js

2017 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

2020 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

2116 ms

wp-polyfill.min.js

wp-polyfill.min.js

2100 ms

hooks.min.js

hooks.min.js

2095 ms

i18n.min.js

i18n.min.js

2014 ms

frontend.min.js

frontend.min.js

1911 ms

waypoints.min.js

waypoints.min.js

1174 ms

core.min.js

core.min.js

1201 ms

frontend.min.js

frontend.min.js

1187 ms

elements-handlers.min.js

elements-handlers.min.js

1185 ms

jet-widgets.js

jet-widgets.js

1186 ms

gtm.js

gtm.js

111 ms

logo.png

logo.png

1126 ms

bg-text.jpg

bg-text.jpg

1126 ms

PORTADAS_WEBSITE_YAMAKI_MAVIC.png

PORTADAS_WEBSITE_YAMAKI_MAVIC.png

1219 ms

PORTADAS_WEBSITE_YAMAKI_SI.png

PORTADAS_WEBSITE_YAMAKI_SI.png

1201 ms

PORTADAS_WEBSITE_YAMAKI_AVIP.png

PORTADAS_WEBSITE_YAMAKI_AVIP.png

1213 ms

AKAI.png

AKAI.png

1149 ms

ALESIS.png

ALESIS.png

1151 ms

ATLONA.png

ATLONA.png

1059 ms

AVIOM.png

AVIOM.png

1141 ms

BLACKMAGIC.png

BLACKMAGIC.png

1071 ms

CARLSBRO.png

CARLSBRO.png

1136 ms

CHAMSYS.png

CHAMSYS.png

1160 ms

CHAUVET-DJ.png

CHAUVET-DJ.png

1177 ms

font

font

40 ms

font

font

75 ms

fa-solid-900.woff

fa-solid-900.woff

1237 ms

font

font

74 ms

fa-regular-400.woff

fa-regular-400.woff

1191 ms

fa-brands-400.woff

fa-brands-400.woff

1255 ms

fa-brands-400.woff

fa-brands-400.woff

1216 ms

Easy-Login.ttf

Easy-Login.ttf

1698 ms

CHAUVET-PORFESSIONAL.png

CHAUVET-PORFESSIONAL.png

1706 ms

DB-AUDIOTECHNIK.png

DB-AUDIOTECHNIK.png

1385 ms

DIRECTOUT.png

DIRECTOUT.png

1027 ms

FURMAN.png

FURMAN.png

1027 ms

GEFEN.png

GEFEN.png

1026 ms

HARTKE.png

HARTKE.png

1105 ms

KORG.png

KORG.png

1093 ms

M-AUDIO.png

M-AUDIO.png

1125 ms

MUXLAB.png

MUXLAB.png

1017 ms

NIVEO.png

NIVEO.png

1022 ms

NORD.png

NORD.png

1024 ms

NUMARK.png

NUMARK.png

1088 ms

PELICAN.png

PELICAN.png

1101 ms

PRESONUS.png

PRESONUS.png

1071 ms

PROEL.png

PROEL.png

1024 ms

Q-SYS.png

Q-SYS.png

1027 ms

QSC.png

QSC.png

969 ms

RADIAL.png

RADIAL.png

1020 ms

MyriadPro-SemiboldIt.woff

MyriadPro-SemiboldIt.woff

1017 ms

SHURE.png

SHURE.png

1011 ms

SOLEX.png

SOLEX.png

1009 ms

TAGIMA.png

TAGIMA.png

1010 ms

TAMBURO.png

TAMBURO.png

1004 ms

TOUCH-ONE.png

TOUCH-ONE.png

1032 ms

VISSONIC.png

VISSONIC.png

1026 ms

VOX.png

VOX.png

967 ms

WAVES.png

WAVES.png

1003 ms

YAMAKI.png

YAMAKI.png

1018 ms

popup-sidebar.jpg

popup-sidebar.jpg

1021 ms

main.js

main.js

183 ms

Accessibility Review

yamaki.com.co accessibility score

82

Accessibility Issues

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

Best Practices

yamaki.com.co best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

yamaki.com.co SEO score

93

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    ES

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yamaki.com.co can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Yamaki.com.co main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

yamaki.com.co

Open Graph data is detected on the main page of Yamaki. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: