5.2 sec in total
541 ms
4.5 sec
204 ms
Click here to check amazing Idiomatic content. Otherwise, check out these important facts you probably never knew about idiomatic.es
Visit idiomatic.esWe analyzed Idiomatic.es page load time and found that the first response time was 541 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
idiomatic.es performance score
name
value
score
weighting
Value3.7 s
28/100
10%
Value12.9 s
0/100
25%
Value10.3 s
8/100
10%
Value7,390 ms
0/100
30%
Value0.031
100/100
15%
Value21.6 s
1/100
10%
541 ms
1394 ms
630 ms
638 ms
634 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 93% of them (69 requests) were addressed to the original Idiomatic.es, 3% (2 requests) were made to Idiomatic.cat and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Idiomatic.es.
Page size can be reduced by 230.8 kB (43%)
535.9 kB
305.1 kB
In fact, the total size of Idiomatic.es main page is 535.9 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. 30% of websites need less resources to load. Images take 250.0 kB which makes up the majority of the site volume.
Potential reduce by 25.9 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 25.9 kB or 77% of the original size.
Potential reduce by 26.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. Idiomatic images are well optimized though.
Potential reduce by 123.0 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 123.0 kB or 68% of the original size.
Potential reduce by 55.6 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. Idiomatic.es needs all CSS files to be minified and compressed as it can save up to 55.6 kB or 79% of the original size.
Number of requests can be reduced by 50 (71%)
70
20
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Idiomatic. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 29 to 1 for CSS and as a result speed up the page load time.
idiomatic.es
541 ms
www.idiomatic.es
1394 ms
codefilter.css
630 ms
aggregator.css
638 ms
jtooltips.css
634 ms
lightbox.css
701 ms
node.css
609 ms
poll.css
606 ms
defaults.css
746 ms
system.css
747 ms
system-menus.css
747 ms
user.css
810 ms
content-module.css
841 ms
filefield.css
957 ms
mollom.css
955 ms
nice_menus.css
943 ms
nice_menus_default.css
944 ms
simplenews.css
948 ms
sitedoc.css
979 ms
superfish.css
1220 ms
superfish-vertical.css
1204 ms
superfish-navbar.css
1203 ms
fckeditor.css
1181 ms
fieldgroup.css
1196 ms
views.css
1231 ms
popups.css
1399 ms
basic.css
1396 ms
spring.css
1357 ms
webform.css
1354 ms
blogbuzz.css
1335 ms
blue.css
1342 ms
jquery.js
1539 ms
drupal.js
1477 ms
es_8b028aabac9a50b3686626b895bcb01d.js
1510 ms
jquery.tooltip.pack.js
1482 ms
lightbox.js
1574 ms
googleanalytics.js
1550 ms
apture.js
14 ms
insertFrame.js
1603 ms
superfish.js
1012 ms
jquery.bgiframe.min.js
1025 ms
jquery.hoverIntent.minified.js
1022 ms
nice_menus.js
1029 ms
poormanscron.js
1060 ms
jquery.hoverIntent.minified.js
1015 ms
jquery.bgiframe.min.js
989 ms
superfish.js
987 ms
supersubs.js
1003 ms
supposition.js
957 ms
sftouchscreen.js
954 ms
jquery.form.js
897 ms
popups.js
894 ms
webform.js
945 ms
en.png
64 ms
fr.png
53 ms
textura6.jpg
523 ms
logo.png
217 ms
map.png
226 ms
ca.png
117 ms
facebook_empresa_traducciones_idiomatic.png
180 ms
bg_menu2.png
145 ms
bg_menu2.png
229 ms
telefono_idiomatic.png
282 ms
edifici.jpg
406 ms
banner_internacionalitzacion.gif
567 ms
informacion_idiomatic_language_services.png
422 ms
logotipo_telefono_idiomatic_language_services.png
466 ms
logotipo_contacto_idiomatic_language_services.png
423 ms
iqnet_certificado_calidad_traduccion_Idiomatic.png
512 ms
proz_associacion_traductores.png
562 ms
ga.js
38 ms
arrows-ffffff.png
543 ms
shadow.png
588 ms
__utm.gif
12 ms
idiomatic.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
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
Links do not have a discernible name
idiomatic.es best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
General
Impact
Issue
Detected JavaScript libraries
idiomatic.es SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Idiomatic.es can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Spanish language. Our system also found out that Idiomatic.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.
idiomatic.es
Open Graph description is not detected on the main page of Idiomatic. 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: