8.5 sec in total
1.6 sec
6.6 sec
218 ms
Click here to check amazing Dead Meet content. Otherwise, check out these important facts you probably never knew about dead-meet.com
Dating/Networking for people in the death industry
Visit dead-meet.comWe analyzed Dead-meet.com page load time and found that the first response time was 1.6 sec and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
dead-meet.com performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value5.8 s
15/100
25%
Value4.2 s
78/100
10%
Value460 ms
61/100
30%
Value0
100/100
15%
Value9.5 s
30/100
10%
1605 ms
136 ms
208 ms
141 ms
173 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 60% of them (56 requests) were addressed to the original Dead-meet.com, 6% (6 requests) were made to Platform.twitter.com and 4% (4 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Dead-meet.com.
Page size can be reduced by 90.2 kB (70%)
129.5 kB
39.3 kB
In fact, the total size of Dead-meet.com main page is 129.5 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. 70% of websites need less resources to load. HTML takes 69.2 kB which makes up the majority of the site volume.
Potential reduce by 53.9 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 53.9 kB or 78% of the original size.
Potential reduce by 236 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. Dead Meet images are well optimized though.
Potential reduce by 98 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 36.0 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. Dead-meet.com needs all CSS files to be minified and compressed as it can save up to 36.0 kB or 84% of the original size.
Number of requests can be reduced by 60 (67%)
90
30
The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dead Meet. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
www.dead-meet.com
1605 ms
wp-emoji-release.min.js
136 ms
validationEngine.jquery.css
208 ms
frontend.css
141 ms
bbpress.css
173 ms
settings.css
166 ms
captions.php
1229 ms
foundation-nonresponsive.min.css
247 ms
font-awesome.min.css
238 ms
prettyPhoto.css
242 ms
default.css
261 ms
style.css
272 ms
responsive.css
381 ms
css
25 ms
form-basic.min.css
425 ms
genericons.css
410 ms
jetpack.css
402 ms
jquery.js
517 ms
jquery-migrate.min.js
487 ms
paid-memberships-pro.js
495 ms
confirm.min.js
521 ms
jquery.themepunch.plugins.min.js
578 ms
jquery.themepunch.revolution.min.js
621 ms
modernizr.foundation.js
636 ms
global.js
604 ms
jscripts.php
1165 ms
deadmeet.css
736 ms
editor.js
728 ms
devicepx-jetpack.js
6 ms
gprofiles.js
57 ms
wpgroho.js
758 ms
foundation.min.js
780 ms
scripts.js
857 ms
app.js
803 ms
comment-reply.min.js
841 ms
widgets.js
86 ms
jscripts-ftr-min.js
874 ms
wp-embed.min.js
893 ms
sharing.js
915 ms
e-201611.js
4 ms
app.css
721 ms
www.dead-meet.com
1337 ms
Dead-Meet-Logo-New.jpg
230 ms
small_logo.png
229 ms
DeadMeet_NewLogo_Slider.jpg
230 ms
2ca6e48dd6e177999cee79560437b424-bpthumb.jpg
232 ms
b6c45598b630597093258bc50fe89da7-bpthumb.jpg
228 ms
defaultav.jpg
490 ms
6b05b899553f463b1382d0a0f482c308-bpthumb.jpg
228 ms
20c5e55e2cb04a6cd0b4ab6bf60f72be-bpthumb.jpg
316 ms
9MhcqozOOK22yTdfTb9Abg.ttf
10 ms
fontawesome-webfont.woff
416 ms
sdk.js
24 ms
gray_pattern.gif
283 ms
up_page.png
284 ms
Genericons.svg
364 ms
8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=
19 ms
widgets.js
181 ms
hovercard.css
47 ms
services.css
84 ms
share
72 ms
g.gif
21 ms
count.json
94 ms
graph.facebook.com
109 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
149 ms
timer.png
164 ms
loader.gif
182 ms
shadow2.png
235 ms
bullet.png
243 ms
large_left.png
244 ms
large_right.png
277 ms
g.gif
55 ms
g.gif
55 ms
g.gif
29 ms
96 ms
xd_arbiter.php
29 ms
xd_arbiter.php
54 ms
syndication
103 ms
462970450461478913
121 ms
1f60d.png
32 ms
1f480.png
29 ms
2665.png
29 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
31 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
60 ms
BMO2aAkE_normal.jpg
42 ms
Wv54sBao_normal.jpg
41 ms
qUXls_bI_normal.jpg
42 ms
CdGkMhcXIAEKiFi.jpg:small
84 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
137 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
146 ms
link_v1_e64f66f5650df987d97cc5f00c4cb5987f367028.svg
28 ms
jot.html
30 ms
print.css
125 ms
dead-meet.com accessibility score
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
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
dead-meet.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
dead-meet.com SEO score
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
DE
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dead-meet.com can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it does not match the claimed English language. Our system also found out that Dead-meet.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.
dead-meet.com
Open Graph data is detected on the main page of Dead Meet. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: