3.6 sec in total
839 ms
2.6 sec
235 ms
Welcome to idstone.es homepage info - get ready to check IDStone best content right away, or after learning these important things about idstone.es
IDStone es un sistema de identificación, trazabilidad y control de stock para la industria de la piedra natural
Visit idstone.esWe analyzed Idstone.es page load time and found that the first response time was 839 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
idstone.es performance score
name
value
score
weighting
Value2.9 s
54/100
10%
Value3.2 s
72/100
25%
Value4.3 s
76/100
10%
Value10 ms
100/100
30%
Value0.009
100/100
15%
Value3.9 s
88/100
10%
839 ms
121 ms
384 ms
236 ms
241 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 88% of them (49 requests) were addressed to the original Idstone.es, 4% (2 requests) were made to Fonts.googleapis.com and 4% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (953 ms) belongs to the original domain Idstone.es.
Page size can be reduced by 486.8 kB (48%)
1.0 MB
522.3 kB
In fact, the total size of Idstone.es main page is 1.0 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. 30% of websites need less resources to load. Images take 463.4 kB which makes up the majority of the site volume.
Potential reduce by 39.1 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. This page needs HTML code to be minified as it can gain 5.2 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 39.1 kB or 79% of the original size.
Potential reduce by 74.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. Obviously, IDStone needs image optimization as it can save up to 74.3 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 279.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 279.1 kB or 73% of the original size.
Potential reduce by 94.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. Idstone.es needs all CSS files to be minified and compressed as it can save up to 94.3 kB or 83% of the original size.
Number of requests can be reduced by 37 (70%)
53
16
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IDStone. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
idstone.es
839 ms
modal.css
121 ms
k2.css
384 ms
shadowbox.css
236 ms
system.css
241 ms
general.css
240 ms
addons.css
246 ms
layout.css
249 ms
template.css
359 ms
joomla.css
366 ms
gk_stuff.css
478 ms
typo.css
392 ms
style1.css
376 ms
style.php
578 ms
mootools-uncompressed.js
953 ms
modal.js
503 ms
k2.js
499 ms
caption.js
503 ms
shadowbox.js
780 ms
gk.script.js
641 ms
engine.js
628 ms
engine_compress.js
630 ms
importer.php
764 ms
mega.css
752 ms
mega.js
795 ms
css
28 ms
css
40 ms
gk_image_show.js
763 ms
jquery.min.js
6 ms
jquery.cookiesdirective.js
877 ms
cookies.js
873 ms
google.js
874 ms
emailButton.png
142 ms
printButton.png
137 ms
pdf_button.png
138 ms
videoIDstoneCapture.jpg
144 ms
videoIDstone.jpg
145 ms
videoIDstoneB2B.jpg
155 ms
logo.png
210 ms
menu_bullet.png
238 ms
SlGVmQWMvZQIdix7AFxXkHNSaA.ttf
18 ms
SlGWmQWMvZQIdix7AFxXmMh3eDs1Yg.ttf
44 ms
header_red_bg.jpg
296 ms
loader.gif
245 ms
arrows.png
254 ms
header_red_bar.jpg
219 ms
nsp_interface.png
295 ms
ga.js
11 ms
__utm.gif
12 ms
user-tools.png
147 ms
1259732008_11_10_Gmoya_0141.jpg
274 ms
408439IMG_0861_b.jpg
335 ms
166022IMG_0867_c.jpg
288 ms
355479IMG_0871.jpg
274 ms
931686IMG_0883_b.jpg
314 ms
424090IMG_0885_b.jpg
372 ms
idstone.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
Form elements do not have associated labels
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.
idstone.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
General
Impact
Issue
Detected JavaScript libraries
idstone.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Idstone.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 Idstone.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.
idstone.es
Open Graph description is not detected on the main page of IDStone. 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: