9 sec in total
437 ms
8.3 sec
280 ms
Visit ifp.es now to see the best up-to-date IFP content for Spain and also check out these interesting facts you probably never knew about ifp.es
¡Triunfa en el mercado laboral con el centro de formación profesional iFP!
Visit ifp.esWe analyzed Ifp.es page load time and found that the first response time was 437 ms and then it took 8.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
ifp.es performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value9.6 s
0/100
25%
Value10.5 s
7/100
10%
Value19,030 ms
0/100
30%
Value0.001
100/100
15%
Value28.7 s
0/100
10%
437 ms
509 ms
199 ms
300 ms
202 ms
Our browser made a total of 136 requests to load all elements on the main page. We found that 67% of them (91 requests) were addressed to the original Ifp.es, 4% (5 requests) were made to Fonts.gstatic.com and 3% (4 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Ifp.es.
Page size can be reduced by 1.9 MB (60%)
3.1 MB
1.3 MB
In fact, the total size of Ifp.es main page is 3.1 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. 55% of websites need less resources to load. Javascripts take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 217.4 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 217.4 kB or 81% of the original size.
Potential reduce by 81.9 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, IFP needs image optimization as it can save up to 81.9 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 1.2 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.2 MB or 70% of the original size.
Potential reduce by 354.4 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. Ifp.es needs all CSS files to be minified and compressed as it can save up to 354.4 kB or 83% of the original size.
Number of requests can be reduced by 47 (38%)
123
76
The browser has sent 123 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IFP. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
ifp.es
437 ms
www.ifp.es
509 ms
css_lQaZfjVpwP_oGNqdtWCSpJT1EMqXdMiU84ekLLxQnc4.css
199 ms
css_7xrSDKkxiLnFEdvbI5OC4j6Gb4qNbT5IiI44wa01lps.css
300 ms
css_Wu8npAzy16WmnnnWKxpexfgsAryolGGaX6yO3GWA5bU.css
202 ms
css_eioaoxBE1qwvdQ27nsG2HlI21tROTEni2_zRn9c_3rQ.css
395 ms
js_MpKfe1sTh5JIVGCZ17DsAuT1rqAC38MLLlkjqjQ1X_k.js
419 ms
js_rfAIP-PWpcNimCqsvZxsphY-rYHBPeSHNJtGvZV1wD8.js
299 ms
js_aNg2i5hIM0FUDif8aaPzi04FhiHyDrXQqxjo53I-pr0.js
392 ms
css
31 ms
addthis_widget.js
16 ms
23
352 ms
js_rPpTNd3kmXPOJ9mchsbAKZ55yyQuYBPHWHYGHzIgdWw.js
691 ms
logo_ifp.png
107 ms
grupo_planeta_logo.png
216 ms
bg_featured_home.jpg
240 ms
centro_autorizado_ifp_0.png
628 ms
actic_bcn.png
603 ms
fbertelsmann_logo_0.png
663 ms
pimec-fondo-claro1.png
712 ms
camara_bcn.png
709 ms
beca_sept.png
933 ms
Intel.png
1163 ms
sanitas.png
1131 ms
aptean.png
1165 ms
Celsa.png
1263 ms
Logo_Caprabo.svg_.png
1267 ms
amma.png
1457 ms
logo_altran_ok.png
1687 ms
clece.png
1697 ms
avpark.png
1726 ms
cirsa.png
1728 ms
emagister.png
1729 ms
pultra.png
2049 ms
udidactics.png
2298 ms
sportium.png
2304 ms
nortia.png
2263 ms
afflelou.png
2273 ms
tecalsa.png
2283 ms
logo_antena_3.png
2662 ms
dkv.png
2855 ms
MSFT_logo_png.png
2885 ms
unipost.jpg
2872 ms
pcbox.png
2835 ms
chiquiTin.png
2960 ms
didakids.png
3296 ms
clibro.png
3492 ms
tecnocom.png
3452 ms
Oub8PRH4QQQ
128 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
54 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
54 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
55 ms
livechat-new.js
44 ms
gtm.js
47 ms
glyphicons-halflings-regular.woff
3076 ms
livechat-cloud-new.js
39 ms
www-embed-player-vflfNyN_r.css
142 ms
www-embed-player.js
168 ms
analytics.js
29 ms
conversion_async.js
29 ms
livechat-v2.js
38 ms
collect
104 ms
170 ms
preferences
354 ms
racc.jpg
3274 ms
asepeyo.png
3257 ms
iframe_api
130 ms
w.js
117 ms
300lo.json
100 ms
get_contact_phone
3307 ms
sh.8e5f85691f9aaa082472a194.html
66 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
62 ms
ad_status.js
51 ms
116 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
113 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
114 ms
clickstream.min.js
59 ms
www-widgetapi.js
58 ms
198 ms
layers.e5ea973510bf60b3db41.js
51 ms
pixel
55 ms
pixel
55 ms
pixel
56 ms
es.js
23 ms
pixel
27 ms
match-result
19 ms
match-result
19 ms
match-result
19 ms
storage.luckyorange.net
74 ms
match-result
42 ms
settings.luckyorange.net
36 ms
ajax-loader-cursor.gif
117 ms
webrtc_theme.js.min.js
5 ms
warning.png
126 ms
boolino.png
3345 ms
postchat-survey.css
24 ms
simon-logo.png
3415 ms
unilever-logo2.png
3394 ms
aymar_i_puig.png
3340 ms
kiko1.png
3327 ms
linde.png
3241 ms
logo_gestionando.png
3449 ms
mutuamontanesa.png
3374 ms
olivaret.png
3406 ms
optimum.png
3305 ms
sage.png
3295 ms
logo_dhl.png
3269 ms
9.jpg
3466 ms
5.jpg
3458 ms
8_0.jpg
3409 ms
6.jpg
3405 ms
7.jpg
3435 ms
1.jpg
3255 ms
2.jpg
3490 ms
marketing-publicidad.jpg
3458 ms
desarrollo-apps-multiplataforma_2.jpg
3454 ms
doble_titulacion_apps_web.jpg
3457 ms
comercio-internacional-transporte-logistica.jpg
3434 ms
decor.png
2744 ms
microinformatica_-_redes.jpg
3194 ms
generica_salo_0.jpg
3501 ms
conferencias.jpg
3460 ms
conoce_ifp_0.png
3727 ms
centro_autorizado_ifp_0.png
3348 ms
actic_bcn.png
3224 ms
fbertelsmann_logo_0.png
3346 ms
pimec-fondo-claro1.png
3393 ms
camara_bcn.png
3381 ms
icon-phone-mobile.png
2960 ms
logo_ifp_2.png
2999 ms
facebook.png
2939 ms
twitter.png
2665 ms
linkedin.png
2624 ms
google_plus.png
2663 ms
youtube.png
2660 ms
tellamamos.png
2689 ms
ifp.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 input fields do not have accessible names
[role] values are not valid
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
ifp.es best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
ifp.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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ifp.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 Ifp.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.
ifp.es
Open Graph description is not detected on the main page of IFP. 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: