2.4 sec in total
79 ms
1.8 sec
545 ms
Click here to check amazing Next After content for United States. Otherwise, check out these important facts you probably never knew about nextafter.com
We partner with nonprofits to build and optimize data-driven fundraising strategies to help you find more donors and make a lasting impact.
Visit nextafter.comWe analyzed Nextafter.com page load time and found that the first response time was 79 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
nextafter.com performance score
name
value
score
weighting
Value7.9 s
0/100
10%
Value11.5 s
0/100
25%
Value8.0 s
21/100
10%
Value1,890 ms
9/100
30%
Value0.029
100/100
15%
Value14.7 s
8/100
10%
79 ms
90 ms
96 ms
546 ms
104 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 31% of them (25 requests) were addressed to the original Nextafter.com, 35% (28 requests) were made to Dmthvvgszra1e.cloudfront.net and 6% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (972 ms) relates to the external source Js.hs-analytics.net.
Page size can be reduced by 2.2 MB (25%)
8.7 MB
6.5 MB
In fact, the total size of Nextafter.com main page is 8.7 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. 85% 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 7.6 MB which makes up the majority of the site volume.
Potential reduce by 43.0 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 43.0 kB or 74% of the original size.
Potential reduce by 1.3 MB
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. Obviously, Next After needs image optimization as it can save up to 1.3 MB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 499.3 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 499.3 kB or 71% of the original size.
Potential reduce by 297.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. Nextafter.com needs all CSS files to be minified and compressed as it can save up to 297.0 kB or 89% of the original size.
Number of requests can be reduced by 20 (27%)
74
54
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Next 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 13 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
nextafter.com
79 ms
wp-emoji-release.min.js
90 ms
pagenavi-css.css
96 ms
bootstrap.min.css
546 ms
style.css
104 ms
mediaqueries.css
106 ms
M9bPKixNLarUMYYydHMz04sSS1L1cjPzdAz08xLjUxKLsvWzimHyyfm5ufl5AA.js
112 ms
bootstrap.min.js
92 ms
load.sumome.com
359 ms
v2.js
86 ms
M9EvL9BNzU1KTdHLzcwDAA.js
110 ms
css
57 ms
css
70 ms
analytics.js
96 ms
fbevents.js
234 ms
nextafter.png
75 ms
Updated_Value_Prop-304x1024.png
246 ms
personal-email-1.jpg
241 ms
personal-email.jpg
270 ms
HLS-1-Direct-480x1024.png
315 ms
Screen-Shot-2016-02-01-at-9.46.11-AM.png
291 ms
Harvest-YE-2-Treatment-478x1024.png
335 ms
Harvest-YE-2-Test-1-Treatment-479x1024.png
382 ms
quotCrappyquot_One-665x1024.png
409 ms
Happy-Thanksgiving-e1449498352780-922x1024.png
424 ms
Hillsdale-treatment-888x1024.png
448 ms
Softer_Calls_to_Action6-495x1024.png
416 ms
T-Positive-423x1024.png
417 ms
T4-330x1024.png
448 ms
Screen-Shot-2015-10-19-at-10.55.45-AM.png
445 ms
ADF-Blog-Treatment-370x1024.png
451 ms
Screen-Shot-2015-09-21-at-9.46.37-AM.png
420 ms
T-1-928x1024.jpg
448 ms
T3-730x1024.png
455 ms
T-Imprimis-Survey-932x1024.png
458 ms
T-443x1024.png
455 ms
T2-464x1024.png
454 ms
social-network.png
219 ms
banner.jpg
595 ms
magnifiying-glass.png
243 ms
TurningLikesIntoDonors_cover-300x259.png
283 ms
bullet.png
265 ms
versus_header1.png
331 ms
arrow-prev-s.png
265 ms
arrow-next-s.png
279 ms
arrow-up-green.png
309 ms
light-bulb.png
286 ms
logo-adf.gif
309 ms
logo-dts.gif
310 ms
logo-heritage.png
373 ms
logo-hillsdake.png
373 ms
logo-hoover.png
372 ms
logo-jesus.png
372 ms
logo-ofl.png
375 ms
dollar-sign.png
408 ms
quote-left.png
411 ms
quote-right.png
412 ms
image.jpeg
447 ms
next.png
413 ms
Facebook1.jpg
416 ms
How-to-Optimize-Email-Acq.jpg
444 ms
nj47mAZe0mYUIySgfn0wpQ.ttf
219 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
264 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
309 ms
4cKlrioa77J2iqTqBgkRWg.ttf
339 ms
Qx6FPcitRwTC_k88tLPc-SbsRidxnYrfzLNRqJkHfFo.ttf
340 ms
linkid.js
147 ms
320257.js
972 ms
358 ms
84da7d07-299f-40de-adeb-0d20539ee771
114 ms
192 ms
collect
99 ms
collect
179 ms
service.js
12 ms
service.js
38 ms
sumome-welcome-popup.css
8 ms
sumome-scrollbox-popup.css
11 ms
css
31 ms
load
208 ms
load
238 ms
nextafter.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.
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
Definition list items are not wrapped in <dl> elements
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
nextafter.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
nextafter.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nextafter.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 Nextafter.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.
nextafter.com
Open Graph data is detected on the main page of Next After. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: