25.1 sec in total
356 ms
24.2 sec
480 ms
Click here to check amazing OpenAIRE content for United States. Otherwise, check out these important facts you probably never knew about openaire.eu
Scientific Knowledge Graph. Scholarly Communication Knowledge Graph. Open scholarly communication infrastructure. European Open Science Cloud. Open Access. Open Data. Open Science
Visit openaire.euWe analyzed Openaire.eu page load time and found that the first response time was 356 ms and then it took 24.7 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
openaire.eu performance score
name
value
score
weighting
Value8.0 s
0/100
10%
Value16.3 s
0/100
25%
Value15.0 s
1/100
10%
Value1,920 ms
8/100
30%
Value0.001
100/100
15%
Value14.8 s
8/100
10%
356 ms
1208 ms
212 ms
333 ms
432 ms
Our browser made a total of 110 requests to load all elements on the main page. We found that 75% of them (83 requests) were addressed to the original Openaire.eu, 10% (11 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (19.8 sec) relates to the external source Apikeys.civiccomputing.com.
Page size can be reduced by 1.3 MB (26%)
4.8 MB
3.6 MB
In fact, the total size of Openaire.eu main page is 4.8 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 3.5 MB which makes up the majority of the site volume.
Potential reduce by 90.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. This page needs HTML code to be minified as it can gain 16.8 kB, which is 14% 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 90.1 kB or 77% of the original size.
Potential reduce by 213.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. OpenAIRE images are well optimized though.
Potential reduce by 311.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 311.9 kB or 70% of the original size.
Potential reduce by 647.3 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. Openaire.eu needs all CSS files to be minified and compressed as it can save up to 647.3 kB or 86% of the original size.
Number of requests can be reduced by 50 (53%)
95
45
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of OpenAIRE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
openaire.eu
356 ms
www.openaire.eu
1208 ms
jcemediabox.css
212 ms
style.css
333 ms
bootstrap.min.css
432 ms
bootstrap-responsive.min.css
327 ms
bootstrap-extended.css
335 ms
style.css
329 ms
bootstrap.css
446 ms
bootstrap-responsive.css
440 ms
jevcustom.css
439 ms
style2.0.css
441 ms
slogin.css
444 ms
jcemediabox.js
645 ms
jquery.min.js
790 ms
jquery-noconflict.js
562 ms
jquery-migrate.min.js
558 ms
bootstrap.min.js
560 ms
engine.jquery.js
561 ms
jquery.simplemodal.js
668 ms
default.js
669 ms
slogin.js
674 ms
mootools-core.js
811 ms
core.js
785 ms
api.js
42 ms
uikit-d49d7f49.js
916 ms
wk-scripts-f06a20ac.js
830 ms
addthis_widget.js
64 ms
theme.css
1002 ms
custom.css
913 ms
uikit.js
912 ms
autocomplete.js
910 ms
search.js
911 ms
sticky.js
1022 ms
tooltip.js
1022 ms
social.js
1022 ms
theme.js
1022 ms
cookieControl-6.2.min.js
933 ms
bootstrap.min.css
102 ms
recaptcha__en_gb.js
63 ms
css
59 ms
css
72 ms
css
86 ms
css
82 ms
Edugain_001.png
168 ms
Orcid_001.png
131 ms
Github_001.png
241 ms
Google_001.jpg
262 ms
Twitter_001.jpg
167 ms
Facebook_001.jpg
167 ms
Linkedin_001.jpg
241 ms
Live_001.png
275 ms
fb.png
273 ms
twitter.png
274 ms
linkedin.png
329 ms
vimeo.png
355 ms
flicker_grey_14.png
367 ms
rss.png
379 ms
slideshare1.png
379 ms
OpenAIREplus_logo.png
380 ms
home.png
434 ms
Banner_Search_contour_web.png
2124 ms
Slide_for_postgrant.gif
1374 ms
Banner_ScienceFree_web.jpg
590 ms
Banner_OpenDataPilot_web.jpg
700 ms
Banner_Zenodo_web.jpg
703 ms
Banner_Monitor_web.jpg
651 ms
bg_white.png
697 ms
Events_images.DI4R_web_banner_690pxnsp-282_links.gif
760 ms
livemarks.png
803 ms
Video_vertical.png
911 ms
facebook_alt.png
809 ms
twitter_alt.png
864 ms
linkedin_alt.png
908 ms
vimeo_alt.png
916 ms
flicker_white_44.png
977 ms
rss_alt.png
1014 ms
OpenAIRE_logo_text_only_white.png
1021 ms
logo-ce-horizontal-en-neg-pantone-lr.png
1022 ms
search_icon_plain.png
1070 ms
b9QBgL0iMZfDSpmcXcE8nNeiznanRB67rGZDYkMvKPc.woff
137 ms
Zd2E9abXLFGSr9G3YK2MsFzqCfRpIA3W6ypxnPISCPA.woff
160 ms
b9QBgL0iMZfDSpmcXcE8nCSLrGe-fkSRw2DeVgOoWcQ.woff
160 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
126 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
127 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
126 ms
CcKI4k9un7TZVWzRVT-T8xsxEYwM7FgeyaSgU71cLG0.woff
123 ms
IczWvq5y_Cwwv_rBjOtT0w.woff
125 ms
xkvoNo9fC8O2RDydKj12bxsxEYwM7FgeyaSgU71cLG0.woff
126 ms
zhcz-_WihjSQC0oHJ9TCYBsxEYwM7FgeyaSgU71cLG0.woff
125 ms
select-arrow-open.png
1000 ms
v
19762 ms
bird.png
984 ms
link_500x500.png
1643 ms
join_500x500.png
1409 ms
monitor_500x400.png
1960 ms
stock-illustration-64155017-dandelions.png
1146 ms
anonymize_2000x360.png
2198 ms
arrowwhite.png
874 ms
piwik.js
686 ms
popup.html
856 ms
tooltip.html
965 ms
300lo.json
84 ms
fontawesome-webfont.woff
1368 ms
sh.953eb77977227bfd253ee158.html
47 ms
anchor
80 ms
styles__ltr.css
12 ms
pmjEM-GhLlUNyebIUFzIQS75e2Oo2a-wD-zEAXBpQqk.js
9 ms
logo_48.png
11 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
10 ms
openaire.eu 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.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
openaire.eu 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
openaire.eu 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
Image elements do not have [alt] attributes
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 Openaire.eu 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 Openaire.eu 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.
openaire.eu
Open Graph description is not detected on the main page of OpenAIRE. 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: