9.7 sec in total
383 ms
8 sec
1.2 sec
Welcome to koex.es homepage info - get ready to check KOEX best content right away, or after learning these important things about koex.es
Somos fabricantes y distribuidores de packaging de lujo. Todo lo que necesitas para la presentación de tus productos. Nos adaptamos a tus necesidades.
Visit koex.esWe analyzed Koex.es page load time and found that the first response time was 383 ms and then it took 9.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
koex.es performance score
name
value
score
weighting
Value5.8 s
4/100
10%
Value18.9 s
0/100
25%
Value26.0 s
0/100
10%
Value14,600 ms
0/100
30%
Value0.031
100/100
15%
Value24.8 s
0/100
10%
383 ms
264 ms
2105 ms
47 ms
419 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Koex.es, 81% (63 requests) were made to Koex-luxury.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Koex-luxury.com.
Page size can be reduced by 126.0 kB (3%)
4.1 MB
4.0 MB
In fact, the total size of Koex.es main page is 4.1 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.7 MB which makes up the majority of the site volume.
Potential reduce by 94.8 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 94.8 kB or 84% of the original size.
Potential reduce by 7.2 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. KOEX images are well optimized though.
Potential reduce by 6.5 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.
Potential reduce by 17.5 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. Koex.es has all CSS files already compressed.
Number of requests can be reduced by 35 (54%)
65
30
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of KOEX. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
koex.es
383 ms
www.koex-luxury.com
264 ms
2105 ms
api.js
47 ms
style.min.css
419 ms
styles.css
521 ms
rs6.css
533 ms
style.css
735 ms
grid.min.css
503 ms
js_composer.min.css
961 ms
jquery.min.js
624 ms
jquery-migrate.min.js
590 ms
rbtools.min.js
1193 ms
rs6.min.js
728 ms
recaptcha__en.js
181 ms
wp-emoji-release.min.js
546 ms
js
290 ms
css
262 ms
flexslider.min.css
525 ms
aos.css
998 ms
ionicons.min.css
1168 ms
style.css
1164 ms
css
278 ms
index.js
1169 ms
index.js
1169 ms
woocommerce-hack.js
1181 ms
js_composer_front.min.js
1183 ms
jquery.flexslider-min.js
1183 ms
imagesloaded.min.js
1187 ms
masonry.min.js
1184 ms
jquery.masonry.min.js
1185 ms
underscore.min.js
1188 ms
aos.js
1259 ms
isotope.pkgd.min.js
1260 ms
jquery.mega-menu.min.js
1261 ms
navigation.js
1277 ms
skip-link-focus-fix.js
1278 ms
owl.carousel.min.js
1260 ms
main.js
1260 ms
PORTADA-scaled.jpg
620 ms
divider-min.png
688 ms
scroll-top.svg
156 ms
logo-koex-blanco.png
153 ms
01-1.jpg
621 ms
02-1.jpg
618 ms
0002_banner_2.jpg
619 ms
02.jpg
1558 ms
07.jpg
714 ms
02-2.jpg
599 ms
03-2.jpg
1551 ms
04-1.jpg
723 ms
05-1.jpg
787 ms
001-1.jpg
721 ms
002-1.jpg
791 ms
003.jpg
792 ms
004-1.jpg
793 ms
005.jpg
1336 ms
0001.jpg
1333 ms
0002.jpg
1334 ms
0003.jpg
1330 ms
0004.jpg
1540 ms
01.jpg
1540 ms
6986896.jpg
1531 ms
7837837.jpg
1533 ms
0101.jpg
2085 ms
002-250x250.jpg
1525 ms
004-250x250.jpg
2080 ms
001-250x250.jpg
2080 ms
analytics.js
435 ms
fondo01.jpg
557 ms
0006.jpg
233 ms
0006.jpg
838 ms
collect
34 ms
0QI6MX1D_JOuGQbT0gvTJPa787weuxJBkqs.woff
543 ms
pxiEyp8kv8JHgFVrJJfedA.woff
543 ms
fontawesome-webfont.woff
716 ms
ionicons.ttf
716 ms
flexslider-icon.woff
173 ms
koex.es accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
koex.es best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
koex.es SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Koex.es can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Koex.es 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.
koex.es
Open Graph data is detected on the main page of KOEX. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: