7.9 sec in total
1.7 sec
5.5 sec
711 ms
Visit magi.es now to see the best up-to-date Magi content and also check out these interesting facts you probably never knew about magi.es
➡️Més de 50 anys formant a conductors a la nostra Autoescola de Vilafranca del Penedès.➡️Els millors tests, per aprovar l'examen de la DGT.
Visit magi.esWe analyzed Magi.es page load time and found that the first response time was 1.7 sec and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
magi.es performance score
name
value
score
weighting
Value5.8 s
4/100
10%
Value10.9 s
0/100
25%
Value10.3 s
8/100
10%
Value1,000 ms
27/100
30%
Value0.063
97/100
15%
Value12.9 s
13/100
10%
1724 ms
114 ms
206 ms
25 ms
39 ms
Our browser made a total of 153 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Magi.es, 17% (26 requests) were made to Maps.google.com and 10% (16 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Autoescolamagi.com.
Page size can be reduced by 1.8 MB (45%)
4.0 MB
2.2 MB
In fact, the total size of Magi.es main page is 4.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. 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 2.1 MB which makes up the majority of the site volume.
Potential reduce by 66.1 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 66.1 kB or 81% of the original size.
Potential reduce by 64.5 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. Magi images are well optimized though.
Potential reduce by 1.4 MB
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 1.4 MB or 68% of the original size.
Potential reduce by 233.1 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. Magi.es needs all CSS files to be minified and compressed as it can save up to 233.1 kB or 84% of the original size.
Number of requests can be reduced by 79 (58%)
136
57
The browser has sent 136 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Magi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 51 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
autoescolamagi.com
1724 ms
wp-emoji-release.min.js
114 ms
cli-style.css
206 ms
css
25 ms
css
39 ms
motioncss.css
211 ms
motioncss-responsive.css
223 ms
font-awesome.css
226 ms
magnific-popup.css
235 ms
fotorama.css
261 ms
style.css
309 ms
responsive.css
320 ms
us_corsa_custom_styles.css
332 ms
jetpack.css
338 ms
jquery.js
583 ms
jquery-migrate.min.js
397 ms
cookielawinfo.js
413 ms
supersized.3.2.7.js
415 ms
photon.js
448 ms
devicepx-jetpack.js
6 ms
gprofiles.js
62 ms
wpgroho.js
447 ms
jquery.easing.min.js
516 ms
jquery.magnific-popup.js
508 ms
supersized.shutter.js
516 ms
waypoints.min.js
558 ms
imagesloaded.js
556 ms
plugins.js
652 ms
us.widgets.js
653 ms
comment-reply.min.js
652 ms
wp-embed.min.js
668 ms
jquery.parallax.js
677 ms
js
28 ms
jquery.gmap.min.js
701 ms
e-201611.js
4 ms
analytics.js
7 ms
linkid.js
8 ms
collect
42 ms
collect
65 ms
ga-audiences
38 ms
intensiu.png
928 ms
curs_hora.png
654 ms
curs_online.png
602 ms
014-e1433175140973.jpg
978 ms
013-e1433175303128.jpg
1122 ms
010-e1433175325800.jpg
1127 ms
curs_intensiu-e1443123045759.jpg
539 ms
006-e1433175150356.jpg
917 ms
018-e1433175255909.jpg
919 ms
012-e1433175314777.jpg
1027 ms
008-e1433175349635.jpg
915 ms
adaptabilitat.png
642 ms
curs_intensiu-e1443123045759.jpg
690 ms
logotip.png
303 ms
web_home_santa.png
1113 ms
015-e1433175273756.jpg
1114 ms
matricula.png
465 ms
collect
8 ms
maps
57 ms
017-e1433347271115.jpg
1268 ms
parallax.png
927 ms
LKf8nhXsWg5ybwEGXk8UBQ.woff
25 ms
0XxGQsSc1g4rdRdjJKZrNBsxEYwM7FgeyaSgU71cLG0.woff
48 ms
f8qltGyj2S-SS_tsOHsjgfesZW2xOQ-xsNqO47m55DA.woff
48 ms
xIAtSaglM8LZOYdGmG1JqQ.woff
48 ms
GpmMKE0dnXylect5ObzLR_esZW2xOQ-xsNqO47m55DA.woff
48 ms
fontawesome-webfont.woff
600 ms
widgets.js
305 ms
overlay.png
215 ms
embed
26 ms
js
252 ms
init_embed.js
201 ms
common.js
28 ms
map.js
40 ms
util.js
41 ms
geocoder.js
40 ms
marker.js
41 ms
hovercard.css
82 ms
services.css
114 ms
g.gif
16 ms
onion.js
29 ms
openhand_8_8.cur
67 ms
AuthenticationService.Authenticate
160 ms
GeocodeService.Search
280 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
63 ms
common.js
41 ms
util.js
72 ms
streetview.js
73 ms
google_white4.png
33 ms
marker.js
50 ms
syndication
128 ms
613334328433614848
383 ms
imagery_viewer.js
113 ms
controls.js
11 ms
GeoPhotoService.GetMetadata
103 ms
transparent.png
84 ms
css
304 ms
geocoder.js
61 ms
sv4.png
165 ms
openhand_8_8.cur
60 ms
mapcnt6.png
160 ms
tmapctrl.png
160 ms
controls.js
18 ms
ViewportInfoService.GetViewportInfo
215 ms
stats.js
10 ms
marker.png
105 ms
css
180 ms
transparent.png
102 ms
infowindow.js
36 ms
google4.png
37 ms
mapcnt6.png
37 ms
sv5.png
37 ms
tmapctrl.png
48 ms
proxy.jpg
182 ms
proxy.jpg
167 ms
proxy.jpg
207 ms
cb_scout5.png
120 ms
tmapctrl4.png
66 ms
imgs8.png
66 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
164 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
183 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
197 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
195 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
56 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
56 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
56 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
110 ms
vt
102 ms
vt
95 ms
vt
95 ms
vt
95 ms
vt
95 ms
vt
142 ms
vt
142 ms
vt
143 ms
vt
142 ms
vt
152 ms
vt
139 ms
vt
173 ms
vt
175 ms
vt
175 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
141 ms
cbk
261 ms
GeoPhotoService.GetMetadata
98 ms
vt
233 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
196 ms
3tIDMGrG_normal.jpg
315 ms
Mv4fgDci_normal.jpg
124 ms
transit_normal.png
126 ms
63c840a051119f6e002366fb9b8b1b3b_normal.jpeg
124 ms
CWxzvAZWUAAj6Ph.jpg
310 ms
CVzsMmQXAAAlwnn.jpg
303 ms
CLeE_MWW8AAbqXd.jpg
310 ms
magi.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-*] attributes do not match their roles
ARIA IDs are not unique
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
magi.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
magi.es SEO score
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
CA
CA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Magi.es can be misinterpreted by Google and other search engines. Our service has detected that Catalan is used on the page, and it matches the claimed language. Our system also found out that Magi.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.
magi.es
Open Graph data is detected on the main page of Magi. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: