9.1 sec in total
98 ms
3.8 sec
5.1 sec
Click here to check amazing Datasets content. Otherwise, check out these important facts you probably never knew about datasets.com
Maximizing the impact of research through openness. Because science works best when research is open.
Visit datasets.comWe analyzed Datasets.com page load time and found that the first response time was 98 ms and then it took 9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
datasets.com performance score
name
value
score
weighting
Value3.9 s
26/100
10%
Value7.3 s
5/100
25%
Value4.5 s
72/100
10%
Value1,740 ms
10/100
30%
Value0.002
100/100
15%
Value12.0 s
16/100
10%
98 ms
229 ms
120 ms
210 ms
217 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Datasets.com, 10% (6 requests) were made to Fonts.gstatic.com and 7% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Static-02.hindawi.com.
Page size can be reduced by 476.0 kB (13%)
3.7 MB
3.2 MB
In fact, the total size of Datasets.com main page is 3.7 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.4 MB which makes up the majority of the site volume.
Potential reduce by 159.5 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 159.5 kB or 83% of the original size.
Potential reduce by 313.8 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. Datasets images are well optimized though.
Potential reduce by 818 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 1.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. Datasets.com needs all CSS files to be minified and compressed as it can save up to 1.9 kB or 13% of the original size.
Number of requests can be reduced by 31 (58%)
53
22
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Datasets. 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 4 to 1 for CSS and as a result speed up the page load time.
www.hindawi.com
98 ms
polyfill.min.js
229 ms
base.css
120 ms
video-js.css
210 ms
osano.js
217 ms
common.8f5ce3b1.chunk.css
218 ms
index.js
341 ms
_app.js
342 ms
webpack-8ed9452df514b4d17d80.js
340 ms
common.833c76e043bbff9f1f05.js
338 ms
basic_page.j~562f23fb.2420dce9081a237d44e5.js
338 ms
main-4b8a1eaa3427aaec1779.js
337 ms
content_alerts~40f38ad1.50b4f2e916cce00c88c0.js
367 ms
main.js.6f15e3a8e78ce265864b.js
367 ms
css
132 ms
gtm.js
550 ms
logo.svg
489 ms
bmri.banner.small.jpg
678 ms
sci.banner.small.jpg
984 ms
mi.banner.small.jpg
985 ms
cmmi.banner.small.jpg
985 ms
home_hero.jpg
1015 ms
MicrosoftTeams-image%20%281%29.png
593 ms
OA-Guide-Global_blog.png
1014 ms
authors.svg
443 ms
publish.svg
441 ms
Blog-banner---Dr-Yuzhen-custom.jpeg
591 ms
%28COPY%29-Blog-banner---Dr-Yuzhen-custom.jpeg
1404 ms
Lead-Guest-Interview-QA_BN.png
1839 ms
generic_icon_3_0.png
974 ms
zYX9KVElMYYaJe8bpLHnCwDKjSL9AIFscQ.ttf
1019 ms
zYXgKVElMYYaJe8bpLHnCwDKhdHeEA.ttf
1019 ms
zYX9KVElMYYaJe8bpLHnCwDKjWr7AIFscQ.ttf
1370 ms
AAAAHAAAAAAAG2wABAAAAAAAAAAAAAAAAAAAADQQAAAAAAAAAAAAAAAIAAAAHAAAlBAAAFQOjAAAETwAABSUAAAQAABEFHAAABAAAAAEXAAAAAAAAAAoAFAAeAEQAiADcARwBigHyAl4CygM+AAEAAAANAFcACwAAAAAAAgAAAAAAAAAAAAAAAAAAAAAAAAAOAK4AAQAAAAAAAQAHAAAAAQAAAAAAAgAHAGAAAQAAAAAAAwAHADYAAQAAAAAABAAHAHUAAQAAAAAABQALABUAAQAAAAAABgAHAEsAAQAAAAAACgAaAIoAAwABBAkAAQAOAAcAAwABBAkAAgAOAGcAAwABBAkAAwAOAD0AAwABBAkABAAOAHwAAwABBAkABQAWACAAAwABBAkABgAOAFIAAwABBAkACgA0AKRpY29tb29uAGkAYwBvAG0AbwBvAG5WZXJzaW9uIDEuMABWAGUAcgBzAGkAbwBuACAAMQAuADBpY29tb29uAGkAYwBvAG0AbwBvAG5pY29tb29uAGkAYwBvAG0AbwBvAG5SZWd1bGFyAFIAZQBnAHUAbABhAHJpY29tb29uAGkAYwBvAG0AbwBvAG5Gb250IGdlbmVyYXRlZCBieSBJY29Nb29uLgBGAG8AbgB0ACAAZwBlAG4AZQByAGEAdABlAGQAIABiAHkAIABJAGMAbwBNAG8AbwBuAC4AAAADAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
92 ms
zYX-KVElMYYaJe8bpLHnCwDKhdTuF6ZM.ttf
1372 ms
zYX7KVElMYYaJe8bpLHnCwDKhdTm5IVcdvfr.ttf
1370 ms
zYX7KVElMYYaJe8bpLHnCwDKhdTmrINcdvfr.ttf
1369 ms
optimize.js
922 ms
bat.js
969 ms
analytics.js
960 ms
fbevents.js
860 ms
ytc.js
933 ms
js
444 ms
hotjar-625463.js
722 ms
uwt.js
543 ms
355556641464051
131 ms
collect
245 ms
collect
237 ms
10076247.json
61 ms
collect
58 ms
26042937.js
212 ms
collect
188 ms
ga-audiences
191 ms
26042937
310 ms
modules.2be88a2123e5e486752f.js
158 ms
box-69edcc3187336f9b0a3fbb4c73be9fe6.html
265 ms
adsct
425 ms
adsct
421 ms
ga-audiences
184 ms
clarity.js
48 ms
c.gif
62 ms
datasets.com 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
Image elements do not have [alt] attributes
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
datasets.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
datasets.com 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 Datasets.com 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 Datasets.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.
datasets.com
Open Graph data is detected on the main page of Datasets. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: