2.9 sec in total
97 ms
2.3 sec
568 ms
Visit nderf.org now to see the best up-to-date NDERF content for France and also check out these interesting facts you probably never knew about nderf.org
Near Death Experience Research Foundation the largest collection of Near Death Experiences (NDE) in over 23 Languages. With thousands of full-text near death experiences posted. Share your near death ...
Visit nderf.orgWe analyzed Nderf.org page load time and found that the first response time was 97 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
nderf.org performance score
name
value
score
weighting
Value3.4 s
37/100
10%
Value10.2 s
0/100
25%
Value11.6 s
4/100
10%
Value7,590 ms
0/100
30%
Value0
100/100
15%
Value16.9 s
5/100
10%
97 ms
57 ms
39 ms
33 ms
48 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 66% of them (69 requests) were addressed to the original Nderf.org, 9% (9 requests) were made to Static.xx.fbcdn.net and 8% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Nderf.org.
Page size can be reduced by 278.3 kB (13%)
2.1 MB
1.8 MB
In fact, the total size of Nderf.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. 75% 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 1.5 MB which makes up the majority of the site volume.
Potential reduce by 79.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. This page needs HTML code to be minified as it can gain 16.8 kB, which is 17% 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 79.5 kB or 81% of the original size.
Potential reduce by 99.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. NDERF images are well optimized though.
Potential reduce by 76.4 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 76.4 kB or 20% of the original size.
Potential reduce by 23.1 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. Nderf.org needs all CSS files to be minified and compressed as it can save up to 23.1 kB or 19% of the original size.
Number of requests can be reduced by 41 (44%)
94
53
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of NDERF. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
nderf.org
97 ms
js
57 ms
css
39 ms
owl.carousel.css
33 ms
owl.transitions.css
48 ms
jackbox.min.css
75 ms
settings.css
75 ms
colorpicker.css
79 ms
bootstrap.min.css
78 ms
theme-animate.css
77 ms
style.css
98 ms
jquery-2.1.0.min.js
103 ms
jquery.queryloader2.min.js
96 ms
google_analytics_auto.js
97 ms
jquery.themepunch.plugins.min.js
99 ms
jquery.themepunch.revolution.min.js
99 ms
jquery.appear.js
95 ms
afterresize.min.js
96 ms
jquery.easing.1.3.js
97 ms
jquery.easytabs.min.js
102 ms
jackbox-packed.min.js
177 ms
jquery.tweet.min.js
109 ms
owl.carousel.min.js
124 ms
flickr.js
124 ms
colorpicker.js
125 ms
theme.plugins.js
125 ms
theme.js
269 ms
js
44 ms
analytics.js
23 ms
reset.css
90 ms
fontello.css
91 ms
collect
147 ms
ga.js
490 ms
od6X2VMAf-U
821 ms
j2Ann0Yyp5E
958 ms
ewuCam31X68
1056 ms
likebox.php
775 ms
shadow.png
465 ms
headerHome.jpg
466 ms
slide_02.jpg
464 ms
181.jpg
465 ms
blueheron.jpg
478 ms
33.jpg
462 ms
jodynderfemail.Png
764 ms
Picture1.jpg
932 ms
Picture2.jpg
903 ms
Picture4.jpg
932 ms
3.jpg
903 ms
118.jpg
765 ms
image_bg_1.png
902 ms
godafterlife.jpg
901 ms
popular.png
930 ms
gfinger.jpg
1079 ms
soulmate.jpg
953 ms
EvidenceSm.jpg
953 ms
image_bg_2.jpg
1077 ms
river_08_tn.jpg
1077 ms
rainbow_01_tn.jpg
1077 ms
tulips_06_tn.jpg
1076 ms
colorfulsunsetoverwater_tn.jpg
1052 ms
010114_tn.jpg
1365 ms
butterfly_38_tn.jpg
1364 ms
20404_tn.jpg
1366 ms
DSCF1323_1_tn.jpg
1364 ms
DSCF6498_1_tn.jpg
1365 ms
butterfly_61_tn.jpg
1365 ms
DSCF5806_1_tn.jpg
1581 ms
butterfly_12_tn.jpg
1581 ms
dw-hst-carina-nebula_tn.jpg
1580 ms
ama00176.jpg
1582 ms
SkinnyBridge.jpg
1582 ms
iands-logo.jpg
1580 ms
nhne-header.png
1170 ms
S6uyw4BMUTPHjx4wWw.ttf
49 ms
S6u9w4BMUTPHh7USSwiPHA.ttf
123 ms
S6u8w4BMUTPHh30AXC-v.ttf
338 ms
S6u9w4BMUTPHh6UVSwiPHA.ttf
339 ms
S6u9w4BMUTPHh50XSwiPHA.ttf
420 ms
S6u_w4BMUTPHjxsI9w2_Gwfo.ttf
420 ms
S6u-w4BMUTPHjxsIPx-oPCc.ttf
420 ms
S6u8w4BMUTPHjxsAXC-v.ttf
419 ms
__utm.gif
22 ms
__utm.gif
16 ms
__utm.gif
13 ms
fontello.woff
1219 ms
Sonia.jpg
1125 ms
dw-nebula_tn.jpg
1126 ms
nderfemail.Png
1126 ms
loader.gif
1124 ms
timer.png
1131 ms
www-player.css
179 ms
www-embed-player.js
202 ms
base.js
363 ms
S5yp7r4Ff9D.css
228 ms
RsWZ-myCkRn.js
295 ms
xjg1QNQguf-.js
327 ms
O9zq51FKpXz.js
326 ms
qnn7MVQZYOT.js
326 ms
5hjr18zii08.js
325 ms
zYzGplAqD4J.js
331 ms
p55HfXW__mM.js
332 ms
348300746_214490084693357_6015785180779050969_n.jpg
569 ms
347581165_1296311451310909_9088729270079560472_n.png
747 ms
UXtr_j2Fwe-.png
475 ms
embed.js
101 ms
nderf.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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
nderf.org 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
nderf.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
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nderf.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 Nderf.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.
nderf.org
Open Graph description is not detected on the main page of NDERF. 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: