3.4 sec in total
466 ms
2.6 sec
355 ms
Welcome to tonex.es homepage info - get ready to check Tonex best content for Spain right away, or after learning these important things about tonex.es
Compre cartuchos de impresora baratos, tóner e impresoras en línea ✅ 24h-Envío ✅ Alternativas de alta calidad ➡️ Haga su pedido ahora y recíbalo lo antes posible!
Visit tonex.esWe analyzed Tonex.es page load time and found that the first response time was 466 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
tonex.es performance score
name
value
score
weighting
Value4.6 s
13/100
10%
Value4.6 s
34/100
25%
Value5.1 s
62/100
10%
Value560 ms
53/100
30%
Value0.001
100/100
15%
Value8.0 s
42/100
10%
466 ms
1075 ms
102 ms
11 ms
70 ms
Our browser made a total of 8 requests to load all elements on the main page. We found that 13% of them (1 request) were addressed to the original Tonex.es, 38% (3 requests) were made to Securepubads.g.doubleclick.net and 25% (2 requests) were made to Cdn.prindo.es. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Prindo.es.
Page size can be reduced by 411.0 kB (59%)
694.7 kB
283.6 kB
In fact, the total size of Tonex.es main page is 694.7 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. Only 5% of websites need less resources to load. HTML takes 496.4 kB which makes up the majority of the site volume.
Potential reduce by 411.0 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 411.0 kB or 83% of the original size.
Potential reduce by 0 B
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.
We found no issues to fix!
6
6
The browser has sent 6 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tonex. According to our analytics all requests are already optimized.
tonex.es
466 ms
www.prindo.es
1075 ms
gpt.js
102 ms
pubads_impl.js
11 ms
ppub_config
70 ms
prindo_white.svg
639 ms
blank.gif
637 ms
gtm.js
996 ms
tonex.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-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
tonex.es best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
tonex.es SEO score
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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tonex.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 Tonex.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.
tonex.es
Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: