3.2 sec in total
433 ms
2.4 sec
347 ms
Visit tilo.es now to see the best up-to-date Tilo content for Spain and also check out these interesting facts you probably never knew about tilo.es
Llevamos mas de 15 años impulsando el sector de la automoción con nuestras mejores soluciones en los procesos digitales. ¡Ven y conócenos!
Visit tilo.esWe analyzed Tilo.es page load time and found that the first response time was 433 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 55% of websites can load faster.
tilo.es performance score
name
value
score
weighting
Value7.7 s
0/100
10%
Value13.6 s
0/100
25%
Value15.8 s
0/100
10%
Value3,760 ms
1/100
30%
Value0.126
83/100
15%
Value18.9 s
3/100
10%
433 ms
301 ms
365 ms
22 ms
40 ms
Our browser made a total of 120 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Tilo.es, 83% (99 requests) were made to Tilomotion.com and 14% (17 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (433 ms) belongs to the original domain Tilo.es.
Page size can be reduced by 147.1 kB (12%)
1.3 MB
1.1 MB
In fact, the total size of Tilo.es main page is 1.3 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 545.2 kB which makes up the majority of the site volume.
Potential reduce by 122.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 122.0 kB or 80% of the original size.
Potential reduce by 0 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. Tilo images are well optimized though.
Potential reduce by 15.5 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. This website has mostly compressed JavaScripts.
Potential reduce by 9.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. Tilo.es has all CSS files already compressed.
Number of requests can be reduced by 81 (87%)
93
12
The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tilo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 48 to 1 for JavaScripts and from 35 to 1 for CSS and as a result speed up the page load time.
tilo.es
433 ms
www.tilomotion.com
301 ms
www.tilomotion.com
365 ms
style.min.css
22 ms
extendify-utilities.css
40 ms
cookie-law-info-public.css
40 ms
cookie-law-info-gdpr.css
43 ms
style.css
42 ms
plugins.min.css
45 ms
modules.min.css
50 ms
font-awesome.min.css
64 ms
style.min.css
66 ms
ionicons.min.css
71 ms
style.css
68 ms
style.css
69 ms
simple-line-icons.css
73 ms
dripicons.css
75 ms
icomoon.css
77 ms
blog.min.css
85 ms
mediaelementplayer-legacy.min.css
75 ms
wp-mediaelement.min.css
79 ms
style_dynamic.css
83 ms
modules-responsive.min.css
81 ms
blog-responsive.min.css
83 ms
style_dynamic_responsive.css
86 ms
css
44 ms
js_composer.min.css
110 ms
tilo-icons.css
98 ms
style.css
96 ms
jquery.min.js
99 ms
jquery-migrate.min.js
149 ms
cookie-law-info-public.js
106 ms
rbtools.min.js
153 ms
rs6.min.js
281 ms
app.js
156 ms
js
79 ms
css
68 ms
style-9921.css
151 ms
forminator-icons.min.css
276 ms
forminator-utilities.min.css
277 ms
forminator-grid.open.min.css
282 ms
forminator-form-default.base.min.css
352 ms
buttons.min.css
268 ms
cookie-law-info-table.css
252 ms
rs6.css
252 ms
core.min.js
316 ms
tabs.min.js
316 ms
accordion.min.js
316 ms
mediaelement-and-player.min.js
301 ms
mediaelement-migrate.min.js
299 ms
wp-mediaelement.min.js
293 ms
modernizr.custom.85257.js
294 ms
jquery.appear.js
292 ms
hoverIntent.min.js
294 ms
jquery.plugin.js
292 ms
jquery.countdown.min.js
291 ms
parallax.min.js
290 ms
select2.min.js
291 ms
easypiechart.js
291 ms
jquery.waypoints.min.js
292 ms
Chart.min.js
285 ms
counter.js
288 ms
fluidvids.min.js
285 ms
jquery.prettyPhoto.min.js
285 ms
jquery.nicescroll.min.js
275 ms
ScrollToPlugin.min.js
273 ms
TweenLite.min.js
272 ms
jquery.mixitup.min.js
266 ms
jquery.waitforimages.js
225 ms
jquery.easing.1.3.js
220 ms
skrollr.js
220 ms
slick.min.js
98 ms
bootstrapCarousel.js
97 ms
jquery.touchSwipe.min.js
98 ms
jquery.multiscroll.min.js
96 ms
typed.js
91 ms
isotope.pkgd.min.js
91 ms
smoothPageScroll.js
90 ms
modules.min.js
101 ms
blog.min.js
95 ms
pxiByp8kv8JHgFVrLCz7Z1JlEw.woff
96 ms
pxiByp8kv8JHgFVrLDD4Z1JlEw.woff
96 ms
pxiByp8kv8JHgFVrLBT5Z1JlEw.woff
410 ms
pxiByp8kv8JHgFVrLEj6Z1JlEw.woff
411 ms
pxiByp8kv8JHgFVrLGT9Z1JlEw.woff
414 ms
pxiEyp8kv8JHgFVrJJnedA.woff
412 ms
pxiByp8kv8JHgFVrLDz8Z1JlEw.woff
411 ms
pxiByp8kv8JHgFVrLFj_Z1JlEw.woff
413 ms
pxiGyp8kv8JHgFVrLPTufntG.woff
410 ms
like.js
349 ms
smush-lazy-load.min.js
348 ms
js_composer_front.min.js
346 ms
jquery.validate.min.js
346 ms
forminator-form.min.js
345 ms
front.multi.min.js
345 ms
TeXGyreAdventor-Regular.woff
355 ms
TeXGyreAdventor-Bold.woff
352 ms
Linearicons-Free.woff
353 ms
ElegantIcons.woff
354 ms
ionicons.ttf
354 ms
tilo-icons.ttf
354 ms
semilla_tilo_loader.svg
353 ms
semilla_header_grande.png
338 ms
dummy.png
353 ms
imagen-home-1-color.jpg
353 ms
imagen-home-2-color.jpg
353 ms
newsletter-home-2x.jpg
307 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrc.woff
237 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrc.woff
239 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrc.woff
241 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrc.woff
239 ms
KFOmCnqEu92Fr1Mu4mxM.woff
240 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
240 ms
KFOkCnqEu92Fr1MmgVxIIzQ.woff
240 ms
KFOlCnqEu92Fr1MmWUlfBBc-.woff
241 ms
logo_tilo_header.png
76 ms
logo_tilo_header_white.png
177 ms
fontawesome-webfont.woff
407 ms
logo_tilo.svg
18 ms
logo_tilo_white.svg
20 ms
tilo.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.
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
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.
tilo.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
Issues were logged in the Issues panel in Chrome Devtools
tilo.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
Image elements do not have [alt] attributes
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 Tilo.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 Tilo.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.
tilo.es
Open Graph data is detected on the main page of Tilo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: