2.6 sec in total
523 ms
1.9 sec
183 ms
Welcome to open-access.net homepage info - get ready to check Open Access best content for Germany right away, or after learning these important things about open-access.net
Das Informationsportal bietet Akteur*innen aus Wissenschaft, Bibliotheken und Verlagen Antworten auf die wichtigsten Fragen zu Open Access.
Visit open-access.netWe analyzed Open-access.net page load time and found that the first response time was 523 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
open-access.net performance score
name
value
score
weighting
Value3.1 s
45/100
10%
Value4.6 s
36/100
25%
Value5.5 s
55/100
10%
Value70 ms
99/100
30%
Value0
100/100
15%
Value4.7 s
80/100
10%
523 ms
490 ms
507 ms
39 ms
202 ms
Our browser made a total of 16 requests to load all elements on the main page. We found that 81% of them (13 requests) were addressed to the original Open-access.net, 6% (1 request) were made to Fonts.googleapis.com and 6% (1 request) were made to Piwik.gwdg.de. The less responsive or slowest element that took the longest time to load (742 ms) relates to the external source Piwik.gwdg.de.
Page size can be reduced by 216.1 kB (57%)
380.8 kB
164.6 kB
In fact, the total size of Open-access.net main page is 380.8 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. 15% of websites need less resources to load. Javascripts take 173.0 kB which makes up the majority of the site volume.
Potential reduce by 31.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 31.4 kB or 72% of the original size.
Potential reduce by 88 B
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. Open Access images are well optimized though.
Potential reduce by 115.3 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 115.3 kB or 67% of the original size.
Potential reduce by 69.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. Open-access.net needs all CSS files to be minified and compressed as it can save up to 69.3 kB or 85% of the original size.
Number of requests can be reduced by 8 (57%)
14
6
The browser has sent 14 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Open Access. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.
523 ms
merged-c2e434009dc4ca104c6be38f31142fd4-5c75ab163236af1b9230b5dd540d0d07.css
490 ms
jquery-1.11.0.min.js
507 ms
css
39 ms
picturefill.min.js
202 ms
ipoa.js
297 ms
piwik.js
742 ms
bg-1.jpg
335 ms
oa.svg
147 ms
deen.png
141 ms
dede.png
143 ms
chde.png
146 ms
chen.png
235 ms
atde.png
238 ms
aten.png
241 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
4 ms
open-access.net 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
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
open-access.net 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
open-access.net SEO score
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
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Open-access.net can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Open-access.net 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.
open-access.net
Open Graph description is not detected on the main page of Open Access. 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: