5.2 sec in total
468 ms
4.6 sec
180 ms
Visit intorex.es now to see the best up-to-date Intorex content and also check out these interesting facts you probably never knew about intorex.es
CNC wood lathes & machining centres
Visit intorex.esWe analyzed Intorex.es page load time and found that the first response time was 468 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
intorex.es performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value8.0 s
2/100
25%
Value9.9 s
10/100
10%
Value860 ms
33/100
30%
Value0.304
39/100
15%
Value8.2 s
41/100
10%
468 ms
1086 ms
539 ms
474 ms
361 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Intorex.es, 78% (45 requests) were made to Intorex.com and 5% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source En.intorex.com.
Page size can be reduced by 415.4 kB (41%)
1.0 MB
604.6 kB
In fact, the total size of Intorex.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. 35% of websites need less resources to load. Images take 503.9 kB which makes up the majority of the site volume.
Potential reduce by 32.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. This page needs HTML code to be minified as it can gain 6.0 kB, which is 14% 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 32.8 kB or 77% of the original size.
Potential reduce by 28.1 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. Intorex images are well optimized though.
Potential reduce by 197.4 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 197.4 kB or 67% of the original size.
Potential reduce by 157.2 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. Intorex.es needs all CSS files to be minified and compressed as it can save up to 157.2 kB or 87% of the original size.
Number of requests can be reduced by 24 (46%)
52
28
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Intorex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
intorex.es
468 ms
en.intorex.com
1086 ms
style.css
539 ms
jquery.js
474 ms
modernizr.min.js
361 ms
css
24 ms
styles.css
241 ms
dcjq-mega-menu.css
247 ms
mappress.css
258 ms
jquery.min.js
28 ms
jquery.dcmegamenu.1.3.4.min.js
258 ms
jquery.ad-gallery.min.js
476 ms
css
15 ms
css
25 ms
slides.min.jquery.js
251 ms
anythingslider.js
396 ms
widgets.js
270 ms
jquery.form.min.js
360 ms
scripts.js
372 ms
jquery.nivo.slider.pack.js
399 ms
jquery.prettyPhoto.js
577 ms
jquery.tipTip.minified.js
578 ms
jquery.lettering.js
578 ms
site.js
579 ms
comment-reply.min.js
579 ms
jquery.lettering.js
465 ms
wp-emoji-release.min.js
155 ms
lupa.png
151 ms
youtubeIcon.png
227 ms
sep_idioms.png
141 ms
thumb.php
370 ms
01.png
141 ms
02.png
141 ms
03.png
160 ms
TC-800-3-1140x339.jpg
671 ms
bg_transp1.png
241 ms
TMC-0301-1140x339.jpg
643 ms
CNX-0122-1140x339.jpg
642 ms
TMC-135-1-1140x339.jpg
690 ms
TMK-008-1-1140x339.jpg
839 ms
hover-magnify.png
490 ms
home1-238x140.png
976 ms
11051801-2-239x140.jpg
772 ms
MV3-002-2-239x140.jpg
773 ms
logo-intorex-open-house-140x1401-50x30.jpg
789 ms
social-twitter-white.png
823 ms
social-flickr-white.png
899 ms
social-facebook-white.png
900 ms
social-flickr2-white.png
908 ms
social-rss-white.png
957 ms
9NUDUckzq40
110 ms
ga.js
38 ms
slider-nav.png
869 ms
s-BiyweUPV0v-yRb-cjciC3USBnSvpkopQaUR-2r7iU.ttf
44 ms
EFpQQyG9GqCrobXxL-KRMfEr6Hm6RMS0v1dtXsGir4g.ttf
45 ms
Sr4SZjJG2shlLRwOkNqcEqCWcynf_cDxXwCLxiixG1c.ttf
45 ms
__utm.gif
25 ms
__utm.gif
4 ms
intorex.es accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
intorex.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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
intorex.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
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
ES
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Intorex.es can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it does not match the claimed English language. Our system also found out that Intorex.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.
intorex.es
Open Graph description is not detected on the main page of Intorex. 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: