6.3 sec in total
971 ms
5.1 sec
266 ms
Visit db.yadvashem.org now to see the best up-to-date Db Yad Vashem content for United States and also check out these interesting facts you probably never knew about db.yadvashem.org
YV360
Visit db.yadvashem.orgWe analyzed Db.yadvashem.org page load time and found that the first response time was 971 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
db.yadvashem.org performance score
name
value
score
weighting
Value0.8 s
100/100
10%
Value0.8 s
100/100
25%
Value1.1 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.8 s
100/100
10%
971 ms
306 ms
1054 ms
324 ms
326 ms
Our browser made a total of 108 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Db.yadvashem.org, 2% (2 requests) were made to S7.addthis.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Yadvashem.org.
Page size can be reduced by 958.5 kB (46%)
2.1 MB
1.1 MB
In fact, the total size of Db.yadvashem.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. 55% of websites need less resources to load. Javascripts take 918.6 kB which makes up the majority of the site volume.
Potential reduce by 75.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 75.4 kB or 76% of the original size.
Potential reduce by 30.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. Db Yad Vashem images are well optimized though.
Potential reduce by 651.0 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 651.0 kB or 71% of the original size.
Potential reduce by 201.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. Db.yadvashem.org needs all CSS files to be minified and compressed as it can save up to 201.3 kB or 86% of the original size.
Number of requests can be reduced by 55 (52%)
106
51
The browser has sent 106 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Db Yad Vashem. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 36 to 1 for CSS and as a result speed up the page load time.
index.asp
971 ms
my_layout.css
306 ms
jquery-1.7.1.min.js
1054 ms
AC_RunActiveContent.js
324 ms
show_hide.js
326 ms
jquery-ui-personalized-1.6rc6.min.js
1365 ms
jquery.galleria.js
751 ms
jquery.lightbox.js
607 ms
chosen.jquery.min.js
761 ms
jquery.cluetip.js
727 ms
jquery.popup.js
760 ms
jquery.social.media.tabs.1.6.1.js
880 ms
thickbox_without_print.js
767 ms
ddaccordion.js
779 ms
simplegallery.js
779 ms
jquery.slideshow.lite-0.8.1.js
896 ms
jquery.prettyPhoto.js
1064 ms
base.css
764 ms
vlist.css
767 ms
its_brain_light.css
880 ms
forms.css
901 ms
basemod.css
916 ms
megamenu.css
917 ms
content.css
1027 ms
yvbase.css
1048 ms
gcs.css
1052 ms
style.css
1064 ms
buttonPro.css
1072 ms
social-bar.css
1173 ms
jquery-sticklr-1.4-light-color.css
1195 ms
lightbox.css
1200 ms
thickbox.css
1207 ms
galleria.css
1211 ms
show_hide.css
1216 ms
slideshow.lite.print.css
1318 ms
slideshow.lite.css
1342 ms
prettyPhoto.css
1347 ms
jquery.popup.css
1348 ms
captionbox.css
1354 ms
addthis_widget.js
12 ms
jquery.cluetip.css
1107 ms
print.css
1175 ms
ui.all.css
1079 ms
SDCLog.js
1065 ms
ui.base.css
152 ms
ui.theme.css
156 ms
ui.core.css
152 ms
ui.accordion.css
154 ms
ui.datepicker.css
154 ms
ui.dialog.css
156 ms
ui.progressbar.css
158 ms
ui.resizable.css
156 ms
ui.slider.css
297 ms
ui.tabs.css
302 ms
analytics.js
70 ms
names.jpg
152 ms
photo.jpg
159 ms
doc_archive.jpg
154 ms
library.jpg
304 ms
visual_center.jpg
158 ms
list_of_list.jpg
502 ms
icon_kristallnacht.jpg
301 ms
icon_otwock.jpg
305 ms
icon_lens.jpg
309 ms
icon_aa.jpg
308 ms
husk.png
597 ms
logo.png
503 ms
wings_new_theme.jpg
503 ms
searchSmall.png
503 ms
icon_database.jpg
504 ms
icon_photo_archive.jpg
608 ms
doc_archive_thumb.jpg
758 ms
icon_righteous.jpg
606 ms
icon_library.jpg
612 ms
icon_vc.jpg
615 ms
icon_lists.jpg
746 ms
icon_deportation.jpg
757 ms
icon_untold_stories.jpg
759 ms
pitel_family.jpg
913 ms
facebook.png
769 ms
youtube.png
896 ms
twitter.png
906 ms
instagram.png
908 ms
pinterest.png
912 ms
rss.png
923 ms
banner_gathering_fragments.jpg
1047 ms
rutka.jpg
1056 ms
auschwitz_album.jpg
1060 ms
facebook.png
1062 ms
twitter.png
1065 ms
youtube.png
1032 ms
collect
12 ms
wtid.js
372 ms
collect
58 ms
blogger.png
1052 ms
pinterest.png
1057 ms
google-plus.png
1059 ms
footer.png
1361 ms
300lo.json
21 ms
loading.gif
726 ms
closelabel.gif
737 ms
icon_print.gif
852 ms
blank.gif
862 ms
select_right.png
871 ms
sh.7c7179124ea24ac6ba46caac.html
29 ms
loading.gif
766 ms
dcs.gif
293 ms
widgets.js
78 ms
db.yadvashem.org accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
db.yadvashem.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
db.yadvashem.org SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Db.yadvashem.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 Db.yadvashem.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.
db.yadvashem.org
Open Graph description is not detected on the main page of Db Yad Vashem. 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: