2.3 sec in total
338 ms
1.4 sec
534 ms
Visit ournextlife.com now to see the best up-to-date Our Next Life content for United States and also check out these interesting facts you probably never knew about ournextlife.com
Financial activism to change the world
Visit ournextlife.comWe analyzed Ournextlife.com page load time and found that the first response time was 338 ms and then it took 1.9 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.
ournextlife.com performance score
name
value
score
weighting
Value6.7 s
2/100
10%
Value30.5 s
0/100
25%
Value56.8 s
0/100
10%
Value68,720 ms
0/100
30%
Value0.006
100/100
15%
Value84.7 s
0/100
10%
338 ms
104 ms
200 ms
152 ms
221 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Ournextlife.com, 19% (10 requests) were made to Ournextlifedotcom.files.wordpress.com and 13% (7 requests) were made to S1.wp.com. The less responsive or slowest element that took the longest time to load (420 ms) relates to the external source S2.wp.com.
Page size can be reduced by 323.5 kB (16%)
2.1 MB
1.7 MB
In fact, the total size of Ournextlife.com 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. 70% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 45.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 45.1 kB or 75% of the original size.
Potential reduce by 2.5 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. Our Next Life images are well optimized though.
Potential reduce by 261.2 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 261.2 kB or 72% of the original size.
Potential reduce by 14.7 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. Ournextlife.com needs all CSS files to be minified and compressed as it can save up to 14.7 kB or 64% of the original size.
Number of requests can be reduced by 21 (55%)
38
17
The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Our Next Life. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
ournextlife.com
338 ms
webfont.js
104 ms
200 ms
css
152 ms
221 ms
247 ms
253 ms
style.css
361 ms
gprofiles.js
112 ms
wpgroho.js
420 ms
414 ms
tiled-gallery.css
331 ms
208 ms
widgets.js
22 ms
348 ms
w.js
22 ms
css
42 ms
wxf0bsv.js
269 ms
merriweather.css
59 ms
our-next-life-logo-color-stacked.jpg
289 ms
cropped-header-for-gazette-theme_fi.jpg
154 ms
163549671.jpeg
321 ms
18395839.jpeg
334 ms
5833031.jpeg
323 ms
104249591.jpeg
360 ms
21567975.jpeg
323 ms
59487175.jpeg
358 ms
22702719.jpeg
357 ms
global-print.css
83 ms
7DI7Kjvwfuz8m3ExKe6m-Q.woff
230 ms
I1Pn3gihk5vyP0Yw5GqKsQ.woff
254 ms
1bHRUMxmJHoup12DnI9XmQ.woff
266 ms
Genericons.svg
85 ms
8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=
16 ms
KYNzioYhDai7mTMnx_gDgv52Zzr6DymnxOm8FeYlfIw.woff
78 ms
11EDm-lum6tskJMBbdy9acAsGe_LvNEZNaQTVcoFuI4.woff
117 ms
TKyx_-JJ6MdpQruNk-t-PNNPDN-hHFbsiA-AAqlOihw.woff
159 ms
WfiXipsmjqRqsDBQ1bA9Cpnqgk0LGBf0izA0nNi1pyI.woff
202 ms
widgets.js
61 ms
ournextlife.com
329 ms
cropped-header-for-gazette-theme_fi.jpg
216 ms
7EvEt60TWcqFZBA31eG0aCitGxHHWxIOYolG3bYUSt6ff5KPgsMdeMJ6Mk6f5Mj.woff
38 ms
Noticons.svg
86 ms
BaABdRAi2AAAA
84 ms
merriweather-bold-webfont.woff
85 ms
merriweather-regular-webfont.woff
84 ms
merriweather-light-webfont.woff
84 ms
hovercard.css
53 ms
services.css
79 ms
g.gif
37 ms
g.gif
38 ms
g.gif
39 ms
p.gif
126 ms
ournextlife.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
Browser errors were logged to the console
ournextlife.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ournextlife.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 Ournextlife.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.
ournextlife.com
Open Graph data is detected on the main page of Our Next Life. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: