3.6 sec in total
360 ms
2.4 sec
851 ms
Welcome to near-death.com homepage info - get ready to check Near Death best content for United States right away, or after learning these important things about near-death.com
A comprehensive collection of information and resources about the Near-Death Experience. Includes a well organized index, a huge collection of NDE accounts, a newsletter, message board and support.
Visit near-death.comWe analyzed Near-death.com page load time and found that the first response time was 360 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
near-death.com performance score
name
value
score
weighting
Value2.5 s
65/100
10%
Value6.3 s
11/100
25%
Value3.2 s
92/100
10%
Value0 ms
100/100
30%
Value0.06
98/100
15%
Value3.0 s
96/100
10%
360 ms
123 ms
186 ms
197 ms
206 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 88% of them (44 requests) were addressed to the original Near-death.com, 8% (4 requests) were made to Pro.fontawesome.com and 2% (1 request) were made to C0.wp.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Near-death.com.
Page size can be reduced by 104.3 kB (7%)
1.6 MB
1.5 MB
In fact, the total size of Near-death.com main page is 1.6 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 1.3 MB which makes up the majority of the site volume.
Potential reduce by 79.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. 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 79.1 kB or 83% of the original size.
Potential reduce by 4.6 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. Near Death images are well optimized though.
Potential reduce by 6.1 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. This website has mostly compressed JavaScripts.
Potential reduce by 14.4 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. Near-death.com needs all CSS files to be minified and compressed as it can save up to 14.4 kB or 13% of the original size.
Number of requests can be reduced by 18 (40%)
45
27
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Near Death. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
near-death.com
360 ms
style.min.css
123 ms
mediaelementplayer-legacy.min.css
186 ms
wp-mediaelement.min.css
197 ms
all.css
206 ms
default.css
141 ms
bootstrap.min.css
256 ms
style.css
192 ms
default.css
195 ms
addtoany.min.css
202 ms
jquery.min.js
33 ms
jquery-migrate.min.js
202 ms
addtoany.min.js
254 ms
main.css
320 ms
jquery-3.4.1.min.js
367 ms
simpleParallax.min.js
337 ms
bootstrap.min.js
337 ms
custom.js
340 ms
e-202418.js
32 ms
main.js
340 ms
lazyload.min.js
341 ms
icon-cart-black.svg
70 ms
fa-brands-400.woff
67 ms
fa-solid-900.woff
91 ms
fa-regular-400.woff
115 ms
fa-light-300.woff
114 ms
feather-search.svg
85 ms
NDE-Logo-Full.svg
90 ms
shutterstock_141118885.jpg
1264 ms
simon-abrams-eMnddgd3pjQ-unsplash-1024x683.jpg
129 ms
bg-experience.jpg
91 ms
icon-experience.svg
87 ms
bg-paranormal.jpg
127 ms
icon-paranormal.svg
130 ms
bg-parascych.jpg
142 ms
icon-parasych.svg
140 ms
bg-philosophy.jpg
190 ms
icon-philosophy.svg
191 ms
bg-psychology.jpg
192 ms
icon-psychology.svg
203 ms
bg-reincarnation.jpg
205 ms
icon-reincarnation.svg
250 ms
bg-religion.jpg
253 ms
icon-religion.svg
254 ms
bg-science.jpg
265 ms
icon-science.svg
265 ms
A_Doctor_Explores.jpg
313 ms
The_Self_Does_Not_Die.jpg
317 ms
Thirty_Years_Of_Investigation.jpg
318 ms
near-death-logo-white.svg
327 ms
near-death.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
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
Heading elements are not in a sequentially-descending order
near-death.com 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
near-death.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
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 Near-death.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 Near-death.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.
near-death.com
Open Graph data is detected on the main page of Near Death. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: