1.5 sec in total
300 ms
1.1 sec
127 ms
Welcome to kezka.es homepage info - get ready to check Kezka best content for Spain right away, or after learning these important things about kezka.es
Venta online de reproducciones de muebles art deco, lámpara Tiffany, escultura en bronce, silla barroca y sillón barroco. Jarrones de hierro fundido medici para el jardín.
Visit kezka.esWe analyzed Kezka.es page load time and found that the first response time was 300 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
kezka.es performance score
name
value
score
weighting
Value2.8 s
57/100
10%
Value4.5 s
37/100
25%
Value7.0 s
32/100
10%
Value680 ms
43/100
30%
Value0
100/100
15%
Value6.3 s
61/100
10%
300 ms
460 ms
153 ms
151 ms
150 ms
Our browser made a total of 24 requests to load all elements on the main page. We found that 8% of them (2 requests) were addressed to the original Kezka.es, 38% (9 requests) were made to Scripts.kezka.com and 33% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (460 ms) belongs to the original domain Kezka.es.
Page size can be reduced by 98.0 kB (58%)
168.8 kB
70.8 kB
In fact, the total size of Kezka.es main page is 168.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Javascripts take 138.3 kB which makes up the majority of the site volume.
Potential reduce by 11.6 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 11.6 kB or 75% of the original size.
Potential reduce by 106 B
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. Kezka images are well optimized though.
Potential reduce by 80.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 80.1 kB or 58% of the original size.
Potential reduce by 6.3 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. Kezka.es needs all CSS files to be minified and compressed as it can save up to 6.3 kB or 79% of the original size.
Number of requests can be reduced by 10 (48%)
21
11
The browser has sent 21 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kezka. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
kezka.es
300 ms
www.kezka.es
460 ms
intro_v22.css
153 ms
jquery-1.7.1.min.js
151 ms
kezka_v22.js
150 ms
ga.js
27 ms
plusone.js
54 ms
botonRegistro.png
24 ms
logoKezka_v1.png
23 ms
textbox_max.png
209 ms
pestaniaCerrada.png
24 ms
logo-locs.png
114 ms
logos.png
117 ms
__utm.gif
27 ms
cb=gapi.loaded_0
9 ms
cb=gapi.loaded_1
22 ms
fastbutton
109 ms
postmessageRelay
117 ms
cb=gapi.loaded_0
16 ms
cb=gapi.loaded_1
16 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
38 ms
3193398744-postmessagerelay.js
24 ms
rpc:shindig_random.js
32 ms
cb=gapi.loaded_0
3 ms
kezka.es accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Links do not have a discernible name
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.
kezka.es best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
kezka.es SEO score
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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kezka.es 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 Kezka.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.
kezka.es
Open Graph description is not detected on the main page of Kezka. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: