Tools & Wizards About Us
futureo.com screenshot

Report Summary

  • 59

    Performance

    Renders faster than
    74% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

futureo.com

FUTUREO-Orientación académica y profesional para vuestro futuro

Page Load Speed

2.9 sec in total

First Response

448 ms

Resources Loaded

2.1 sec

Page Rendered

358 ms

futureo.com screenshot

About Website

Click here to check amazing FUTUREO content. Otherwise, check out these important facts you probably never knew about futureo.com

¿No sabéis que pasos seguir para decidir vuestra orientación?Acompañamiento en orientación por expertos de la educación. Descubre el método FUTUREO en 3 etapas.

Visit futureo.com

Key Findings

We analyzed Futureo.com page load time and found that the first response time was 448 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

futureo.com performance score

59

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

10/100

25%

SI (Speed Index)

Value7.6 s

25/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value5.1 s

76/100

10%

Network Requests Diagram

futureo.com

448 ms

5ba542059e60ca66985bccdba7c14e6d.css

179 ms

jquery.min.js

315 ms

jquery-migrate.min.js

236 ms

bootstrap.bundle.min.js

340 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 66% of them (39 requests) were addressed to the original Futureo.com, 31% (18 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Futureo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 62.0 kB (13%)

Content Size

476.6 kB

After Optimization

414.6 kB

  • HTML
  • Images

In fact, the total size of Futureo.com main page is 476.6 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. 60% of websites need less resources to load. Images take 403.9 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 55.5 kB

  • Original 72.8 kB
  • After minification 69.6 kB
  • After compression 17.3 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 55.5 kB or 76% of the original size.

Image Optimization

-2%

Potential reduce by 6.6 kB

  • Original 403.9 kB
  • After minification 397.3 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. FUTUREO images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 22 (59%)

Requests Now

37

After Optimization

15

  • Images
  • JavaScript
  • CSS

The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FUTUREO. 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 as a result speed up the page load time.

Network Requests Diagram

futureo.com

futureo.com

448 ms

5ba542059e60ca66985bccdba7c14e6d.css

5ba542059e60ca66985bccdba7c14e6d.css

179 ms

jquery.min.js

jquery.min.js

315 ms

jquery-migrate.min.js

jquery-migrate.min.js

236 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

340 ms

jquery.fancybox.js

jquery.fancybox.js

301 ms

slick.min.js

slick.min.js

300 ms

all.min.js

all.min.js

612 ms

modernizr.js

modernizr.js

316 ms

jquery.mobile.touch.min.js

jquery.mobile.touch.min.js

339 ms

js-cookie.js

js-cookie.js

342 ms

scripts.js

scripts.js

394 ms

js

js

68 ms

wp-embed.min.js

wp-embed.min.js

393 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

408 ms

wp-polyfill.min.js

wp-polyfill.min.js

416 ms

dom-ready.min.js

dom-ready.min.js

425 ms

hooks.min.js

hooks.min.js

466 ms

i18n.min.js

i18n.min.js

469 ms

a11y.min.js

a11y.min.js

493 ms

jquery.json.min.js

jquery.json.min.js

500 ms

gravityforms.min.js

gravityforms.min.js

511 ms

placeholders.jquery.min.js

placeholders.jquery.min.js

550 ms

asyncdc.min.js

asyncdc.min.js

550 ms

lazyload.min.js

lazyload.min.js

573 ms

css2

css2

44 ms

gif.gif

gif.gif

619 ms

curveb.svg

curveb.svg

386 ms

curve.svg

curve.svg

411 ms

equipe.jpg

equipe.jpg

1036 ms

top-footer-curve.svg

top-footer-curve.svg

442 ms

bottom-footer-curve.svg

bottom-footer-curve.svg

471 ms

7cH1v4okm5zmbvwkAx_sfcEuiD8jvvKcPg.ttf

7cH1v4okm5zmbvwkAx_sfcEuiD8jvvKcPg.ttf

322 ms

7cH1v4okm5zmbvwkAx_sfcEuiD8jjPKcPg.ttf

7cH1v4okm5zmbvwkAx_sfcEuiD8jjPKcPg.ttf

182 ms

7cH1v4okm5zmbvwkAx_sfcEuiD8j4PKcPg.ttf

7cH1v4okm5zmbvwkAx_sfcEuiD8j4PKcPg.ttf

99 ms

7cH1v4okm5zmbvwkAx_sfcEuiD8jPvKcPg.ttf

7cH1v4okm5zmbvwkAx_sfcEuiD8jPvKcPg.ttf

125 ms

7cH1v4okm5zmbvwkAx_sfcEuiD8jvvOcPg.ttf

7cH1v4okm5zmbvwkAx_sfcEuiD8jvvOcPg.ttf

431 ms

7cH1v4okm5zmbvwkAx_sfcEuiD8jYPWcPg.ttf

7cH1v4okm5zmbvwkAx_sfcEuiD8jYPWcPg.ttf

106 ms

7cH1v4okm5zmbvwkAx_sfcEuiD8jWfWcPg.ttf

7cH1v4okm5zmbvwkAx_sfcEuiD8jWfWcPg.ttf

191 ms

7cH1v4okm5zmbvwkAx_sfcEuiD8jPvWcPg.ttf

7cH1v4okm5zmbvwkAx_sfcEuiD8jPvWcPg.ttf

153 ms

7cH1v4okm5zmbvwkAx_sfcEuiD8jF_WcPg.ttf

7cH1v4okm5zmbvwkAx_sfcEuiD8jF_WcPg.ttf

170 ms

fa-solid-900.woff

fa-solid-900.woff

399 ms

fa-regular-400.woff

fa-regular-400.woff

410 ms

7cH3v4okm5zmbtYtMeA0FKq0Jjg2drF0fdC6.ttf

7cH3v4okm5zmbtYtMeA0FKq0Jjg2drF0fdC6.ttf

127 ms

7cH3v4okm5zmbtYtMeA0FKq0Jjg2drFGfdC6.ttf

7cH3v4okm5zmbtYtMeA0FKq0Jjg2drFGfdC6.ttf

138 ms

7cH3v4okm5zmbtYtMeA0FKq0Jjg2drEqfdC6.ttf

7cH3v4okm5zmbtYtMeA0FKq0Jjg2drEqfdC6.ttf

188 ms

7cH3v4okm5zmbtYtMeA0FKq0Jjg2drH0fdC6.ttf

7cH3v4okm5zmbtYtMeA0FKq0Jjg2drH0fdC6.ttf

180 ms

7cH3v4okm5zmbtYtMeA0FKq0Jjg2drF0fNC6.ttf

7cH3v4okm5zmbtYtMeA0FKq0Jjg2drF0fNC6.ttf

202 ms

7cH3v4okm5zmbtYtMeA0FKq0Jjg2drGqetC6.ttf

7cH3v4okm5zmbtYtMeA0FKq0Jjg2drGqetC6.ttf

171 ms

7cH3v4okm5zmbtYtMeA0FKq0Jjg2drGTetC6.ttf

7cH3v4okm5zmbtYtMeA0FKq0Jjg2drGTetC6.ttf

269 ms

7cH3v4okm5zmbtYtMeA0FKq0Jjg2drH0etC6.ttf

7cH3v4okm5zmbtYtMeA0FKq0Jjg2drH0etC6.ttf

275 ms

7cH3v4okm5zmbtYtMeA0FKq0Jjg2drHdetC6.ttf

7cH3v4okm5zmbtYtMeA0FKq0Jjg2drHdetC6.ttf

228 ms

fa-brands-400.woff

fa-brands-400.woff

517 ms

logo.svg

logo.svg

177 ms

pic-loupe.svg

pic-loupe.svg

187 ms

picto-profundizar-site-web-carre-900x900-v2.png

picto-profundizar-site-web-carre-900x900-v2.png

187 ms

pic-cible.svg

pic-cible.svg

262 ms

pic-contact.svg

pic-contact.svg

264 ms

logo-footer.svg

logo-footer.svg

273 ms

Accessibility Review

futureo.com accessibility score

76

Accessibility Issues

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

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

futureo.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

futureo.com SEO score

93

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    ES

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Futureo.com 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 Futureo.com 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.

Social Sharing Optimization

futureo.com

Open Graph data is detected on the main page of FUTUREO. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: