2.2 sec in total
399 ms
1.4 sec
427 ms
Click here to check amazing After content for India. Otherwise, check out these important facts you probably never knew about after.me
For Free, create text or Video inheritance Will. Create deferred emails that will be sent out to your loved ones after your death. Physical document storage etc.
Visit after.meWe analyzed After.me page load time and found that the first response time was 399 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
after.me performance score
name
value
score
weighting
Value6.8 s
1/100
10%
Value6.8 s
7/100
25%
Value9.5 s
11/100
10%
Value160 ms
93/100
30%
Value0.047
99/100
15%
Value9.5 s
30/100
10%
399 ms
19 ms
275 ms
341 ms
488 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 97% of them (56 requests) were addressed to the original After.me, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (488 ms) belongs to the original domain After.me.
Page size can be reduced by 87.2 kB (66%)
133.1 kB
45.9 kB
In fact, the total size of After.me main page is 133.1 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. 50% of websites need less resources to load. Javascripts take 63.5 kB which makes up the majority of the site volume.
Potential reduce by 36.2 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 13.5 kB, which is 30% 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 36.2 kB or 80% of the original size.
Potential reduce by 423 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. After images are well optimized though.
Potential reduce by 35.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 35.0 kB or 55% of the original size.
Potential reduce by 15.6 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. After.me needs all CSS files to be minified and compressed as it can save up to 15.6 kB or 84% of the original size.
Number of requests can be reduced by 21 (37%)
57
36
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of After. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and as a result speed up the page load time.
after.me
399 ms
analytics.js
19 ms
css
275 ms
jquery-1.9.1.js
341 ms
jquery-1.10.3-ui.min.js
488 ms
plupload.full.js
233 ms
plupload.js
118 ms
plupload.html5.js
106 ms
jquery.unobtrusive-ajax.js
142 ms
jquery.validate.min.js
207 ms
jquery.validate.unobtrusive.min.js
181 ms
common-ajax.js
250 ms
custom.js
237 ms
select2.min.js
328 ms
bootstrap.js
307 ms
bootstrap-tooltip.js
348 ms
bootstrap-popover.js
344 ms
bootstrap-modal.js
357 ms
bootstrap-modalmanager.js
367 ms
jquery.validate.js
395 ms
layerslider.css
387 ms
jquery-easing-1.3.js
405 ms
jquery-transit-modified.js
418 ms
layerslider.transitions.js
468 ms
layerslider.kreaturamedia.jquery.js
458 ms
collect
20 ms
bx_loader.gif
107 ms
bg.png
116 ms
header-shedow.png
112 ms
logo.png
112 ms
nav-line.png
113 ms
skin.css
41 ms
loader.gif
70 ms
slider-bg.jpg
70 ms
slide1.jpg
69 ms
slide2.png
104 ms
validation_icon.gif
32 ms
title-line-bg.jpg
80 ms
98f0ec21-cfc0-4e0a-9263-839077495d46.jpg
98 ms
d8e7e665-cd3b-4378-afa6-e04748bdf6ae.jpg
105 ms
checkbox.png
150 ms
1.png
130 ms
2.jpg
198 ms
3.png
167 ms
4.png
157 ms
5.jpg
290 ms
6.jpg
170 ms
user.png
198 ms
testimonial-left.png
204 ms
testimonial-right.png
211 ms
274a0a8b-50f3-4684-8f65-742a2ff152ed.jpg
290 ms
87c3fd0a-9f48-4a5d-9718-bd15e475f01b.jpg
324 ms
183e58d2-83eb-4e5c-9597-9399510491a5.jpg
328 ms
de7a55bf-ff07-4c2a-94b4-d8e1c8810daf.png
288 ms
d91c3cf3-2d3f-40da-8926-05cf1d13dd91.jpg
373 ms
452afc45-b333-4663-8d3a-148b41cde0ed.jpg
310 ms
ft-icns.png
369 ms
skin.png
73 ms
after.me 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
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
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
Image elements do not have [alt] attributes
Links do not have a discernible name
after.me 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
Browser errors were logged to the console
after.me 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
robots.txt is not valid
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise After.me can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that After.me 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.
after.me
Open Graph description is not detected on the main page of After. 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: