5.6 sec in total
560 ms
3.9 sec
1.1 sec
Visit toyota.pt now to see the best up-to-date Toyota content for Portugal and also check out these interesting facts you probably never knew about toyota.pt
Descubra a gama de automóveis e serviços que a Toyota Portugal tem disponível para si. Se está a pensar comprar um carro, novo ou usado, visite-nos já!
Visit toyota.ptWe analyzed Toyota.pt page load time and found that the first response time was 560 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
toyota.pt performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value16.5 s
0/100
25%
Value13.1 s
2/100
10%
Value3,180 ms
2/100
30%
Value0
100/100
15%
Value16.0 s
6/100
10%
560 ms
764 ms
135 ms
314 ms
295 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 35% of them (29 requests) were addressed to the original Toyota.pt, 7% (6 requests) were made to T1-cms-2.images.toyota-europe.com and 6% (5 requests) were made to T1-cms-4.images.toyota-europe.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source T1-carassets-1.toyota-europe.com.
Page size can be reduced by 1.6 MB (23%)
7.0 MB
5.4 MB
In fact, the total size of Toyota.pt main page is 7.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. 60% of websites need less resources to load. Images take 5.7 MB which makes up the majority of the site volume.
Potential reduce by 141.5 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 30.8 kB, which is 19% 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 141.5 kB or 86% of the original size.
Potential reduce by 697.6 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, Toyota needs image optimization as it can save up to 697.6 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 765.9 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 765.9 kB or 69% of the original size.
Number of requests can be reduced by 28 (37%)
75
47
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Toyota. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.toyota.pt
560 ms
www.toyota.pt
764 ms
T1-style.css
135 ms
modernizr.custom.12394.js
314 ms
special.includes.js
295 ms
settings
356 ms
vendor-basics.js
357 ms
vendor-ext.js
348 ms
require.js
241 ms
app.js
362 ms
tcm-3032-4973-64
389 ms
T1-skrollr.css
107 ms
T1-skrollr-xlg.css
111 ms
3bd4c547-ee58-4750-976c-5ee2e61d07f8.PNG
753 ms
d6b4c6f4-8d70-4a14-97e7-b846564e5e02.PNG
749 ms
b0766c2b-c2b8-4125-839d-ab1bdb89d17c.PNG
752 ms
toyota-prius-2015-miniatura_tcm-3032-586430.png
690 ms
44348c33-1ee0-4d90-8920-e8763a976259.PNG
750 ms
verdades-hbridos-toyota_tcm-3032-278407.jpg
810 ms
conduzir-um-hibrido_tcm-3032-278412.jpg
811 ms
hqdefault.jpg
493 ms
8aa57494-7d8f-479d-8621-5af3d9942e67.PNG
748 ms
e162a725-6d62-46b3-a442-c40953ac4e1e.PNG
747 ms
fb7cf711-ecd2-4301-bacf-7763eebb7fbc.PNG
805 ms
hqdefault.jpg
614 ms
hqdefault.jpg
748 ms
hqdefault.jpg
744 ms
H%C3%ADbridosInterparesTaxonomia_tcm-3032-638940.jpg
813 ms
Destaque%20Square%20Collection%20Taxonomy_tcm-3032-611026.jpg
1046 ms
RAV4-HYB-Taxonomy-555x249_tcm-3032-499005.jpg
803 ms
d76867de-4316-402e-8800-de15f322c7a9.PNG
685 ms
b2588d1b-9b6b-47a9-9fe7-e8810b2a47a8.PNG
686 ms
f4b97d62-5cf0-49f1-8e0e-87a02cef83dc.PNG
683 ms
51e5232c-2531-4398-b7a5-600af7d018b7.PNG
743 ms
toyota-hybrid-prius-movie-2-spotlight_tcm-3032-59880.jpg
744 ms
carregar-um-hibrido_tcm-3032-278416.jpg
806 ms
novos-modelos-genebra-taxonomia_tcm-3032-634983.jpg
802 ms
simplicidade-de-um-hibrido_tcm-3032-278409.jpg
803 ms
Taxonomia_Dakar-2015_tcm-3032-598576.jpg
805 ms
2fab5836-af57-439f-9d20-c4fa019598b0.PNG
682 ms
197783fc-af9d-4646-8772-33c56614bb6d.PNG
800 ms
719f6f2c-5b03-4b79-9f93-aa9a83409f51.PNG
1472 ms
tag.js
251 ms
logo-medium_tcm-3032-137260.png
728 ms
logo-small_tcm-3032-137261.png
702 ms
focuswindow_pre_inspecao_tcm-3032-471439.jpg
775 ms
CarouselNav.png
230 ms
logo_PTPT_153x90_tcm-3032-201032.png
642 ms
focuswindow_marcacoesonline_tcm-3032-471438.jpg
764 ms
3.focuswindow_rav4_tcm-3032-633658.jpg
773 ms
1.focuswindow_square_3_tcm-3032-611612.png
770 ms
ImagemTopo-CarroDeSonho2015_tcm-3032-518448.jpg
775 ms
Focuswindow-5%2B_tcm-3032-431740.jpg
767 ms
_Incapsula_Resource
261 ms
toyotatext_bd.woff
427 ms
toyotatext_rg.woff
486 ms
toyotadisplay_bd.woff
429 ms
toyotadisplay_rg.woff
490 ms
Toyota-icon.woff
376 ms
tag
541 ms
postal.min.js
532 ms
_Incapsula_Resource
129 ms
T1-skrollr-sm.css
223 ms
lodash.min.js
14 ms
postalPostMessage.js
132 ms
video.min.js
119 ms
t1-loader.gif
124 ms
T1-skrollr-md-width-sm-height.css
112 ms
T1-skrollr-md.css
113 ms
T1-skrollr-lg-width-sm-height.css
120 ms
T1-skrollr-lg.css
111 ms
nr-852.min.js
75 ms
ef68ae4fe5cc91e98d24a79c880b34def7f18aca.js
46 ms
analytics.js
95 ms
conversion_async.js
73 ms
wtid.js
30 ms
fba316b5e4
135 ms
66 ms
linkid.js
31 ms
dcs.gif
7 ms
collect
22 ms
collect
58 ms
60 ms
ga-audiences
20 ms
toyota.pt 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
Links do not have a discernible name
toyota.pt 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
toyota.pt 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 doesn't use legible font sizes
PT
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Toyota.pt can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Toyota.pt 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.
toyota.pt
Open Graph data is detected on the main page of Toyota. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: