3.3 sec in total
78 ms
3.1 sec
140 ms
Visit futureofed.org now to see the best up-to-date Future Ofed content and also check out these interesting facts you probably never knew about futureofed.org
Explore future possibilities for education with KnowledgeWorks forecasts, guides and futures thinking tools.
Visit futureofed.orgWe analyzed Futureofed.org page load time and found that the first response time was 78 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
futureofed.org performance score
name
value
score
weighting
Value5.4 s
6/100
10%
Value7.0 s
6/100
25%
Value5.9 s
48/100
10%
Value560 ms
53/100
30%
Value0
100/100
15%
Value10.4 s
24/100
10%
78 ms
683 ms
194 ms
52 ms
106 ms
Our browser made a total of 126 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Futureofed.org, 75% (94 requests) were made to Knowledgeworks.org and 5% (6 requests) were made to App-sjg.marketo.com. The less responsive or slowest element that took the longest time to load (683 ms) relates to the external source Knowledgeworks.org.
Page size can be reduced by 1.4 MB (67%)
2.1 MB
683.2 kB
In fact, the total size of Futureofed.org main page is 2.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. 60% of websites need less resources to load. Javascripts take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 137.6 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 137.6 kB or 78% of the original size.
Potential reduce by 6.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. Future Ofed images are well optimized though.
Potential reduce by 887.1 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 887.1 kB or 65% of the original size.
Potential reduce by 365.9 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. Futureofed.org needs all CSS files to be minified and compressed as it can save up to 365.9 kB or 84% of the original size.
Number of requests can be reduced by 101 (85%)
119
18
The browser has sent 119 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Future Ofed. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 63 to 1 for JavaScripts and from 34 to 1 for CSS and as a result speed up the page load time.
futureofed.org
78 ms
future-learning
683 ms
jquery.min.js
194 ms
jquery.once.js
52 ms
drupal.js
106 ms
jquery.ui.core.min.js
53 ms
jquery.ui.widget.min.js
75 ms
jquery.ui.accordion.min.js
126 ms
jquery.ui.button.min.js
125 ms
jquery.ui.mouse.min.js
131 ms
jquery.ui.draggable.min.js
221 ms
jquery.ui.position.min.js
177 ms
jquery.ui.resizable.min.js
227 ms
jquery.ui.dialog.min.js
220 ms
ajax.js
250 ms
jquery_update.js
230 ms
bootstrap.min.js
6 ms
accordion_init.js
226 ms
jquery.colorbox-min.js
251 ms
colorbox.js
241 ms
colorbox_default_style.js
255 ms
colorbox_load.js
261 ms
scroll_to_top.js
273 ms
simple_dialog.js
303 ms
video.js
284 ms
custom_search.js
300 ms
collapse.js
300 ms
form.js
306 ms
googleanalytics.js
321 ms
widgets.js
469 ms
_progress.js
357 ms
colorbox_node.js
369 ms
superfish.js
357 ms
supposition.js
359 ms
jquery.hoverIntent.minified.js
366 ms
supersubs.js
394 ms
superfish.js
395 ms
affix.js
406 ms
bootstrap.min.css
6 ms
system.base.css
411 ms
jquery.ui.core.min.css
389 ms
jquery.ui.theme.min.css
442 ms
forms2.min.js
25 ms
addthis_widget.js
13 ms
jquery.ui.accordion.min.css
367 ms
jquery.ui.button.min.css
376 ms
jquery.ui.resizable.min.css
385 ms
jquery.ui.dialog.min.css
386 ms
scroll_to_top.css
395 ms
calendar_multiday.css
401 ms
colorbox_node.css
320 ms
date.css
315 ms
datepicker.1.7.css
332 ms
date_repeat_field.css
335 ms
field.css
346 ms
views.css
347 ms
ckeditor.css
333 ms
accordion_init.css
350 ms
colorbox_default_style.css
343 ms
ctools.css
354 ms
simple_dialog.css
349 ms
video.css
347 ms
custom_search.css
339 ms
superfish.css
362 ms
superfish-vertical.css
342 ms
overrides.css
376 ms
style.css
558 ms
ga.js
7 ms
alert.js
351 ms
__utm.gif
14 ms
button.js
313 ms
carousel.js
352 ms
collapse.js
372 ms
dropdown.js
355 ms
modal.js
377 ms
tooltip.js
378 ms
popover.js
365 ms
scrollspy.js
363 ms
tab.js
364 ms
transition.js
358 ms
ajax.js
369 ms
respond.min.js
401 ms
bootstrap.js
374 ms
kw.js
371 ms
css
33 ms
font-awesome.min.css
26 ms
munchkin.js
53 ms
munchkin.js
108 ms
logo-bnw.svg
106 ms
fol_2.png
65 ms
knowledgeworks-forecast-4.JPG
339 ms
education_playbook.JPG
108 ms
forecast-cover.JPG
109 ms
future-workforce.JPG
61 ms
cultivating-eqitable-learning-ecosystems-th.jpg
107 ms
certifying-future-credentials_0.jpg
155 ms
edworks.svg
151 ms
strive-logo.svg
340 ms
kw-logo-footer.png
154 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
43 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
44 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
44 ms
fontawesome-webfont.woff
43 ms
glyphicons-halflings-regular.woff
282 ms
glyphicons-halflings-regular.woff
41 ms
visitWebPage
278 ms
getForm
396 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
191 ms
up-arrow.png
148 ms
ui-bg_flat_75_ffffff_40x100.png
148 ms
ui-icons_222222_256x240.png
150 ms
ui-bg_highlight-soft_75_cccccc_1x100.png
148 ms
arrows-ffffff.png
150 ms
syndication
110 ms
350280693198245888
128 ms
forms2.css
17 ms
forms2-theme-simple.css
16 ms
css
13 ms
XDFrame
305 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
253 ms
boost
10 ms
300lo.json
36 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
239 ms
sh.07f0d9bf220d07a763adad1e.html
25 ms
layers.173914a8ea2767730b7b.js
28 ms
forms2.min.js
28 ms
futureofed.org accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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 IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
futureofed.org 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
futureofed.org 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 uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Futureofed.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Futureofed.org 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.
futureofed.org
Open Graph description is not detected on the main page of Future Ofed. 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: