7.1 sec in total
2 sec
4.8 sec
216 ms
Welcome to nealepetersen.com homepage info - get ready to check Nealepetersen best content right away, or after learning these important things about nealepetersen.com
Visit nealepetersen.comWe analyzed Nealepetersen.com page load time and found that the first response time was 2 sec and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
nealepetersen.com performance score
2024 ms
581 ms
25 ms
37 ms
568 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 62% of them (33 requests) were addressed to the original Nealepetersen.com, 9% (5 requests) were made to Fonts.gstatic.com and 6% (3 requests) were made to S.gravatar.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Nealepetersen.com.
Page size can be reduced by 669.8 kB (57%)
1.2 MB
504.2 kB
In fact, the total size of Nealepetersen.com main page is 1.2 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. 40% of websites need less resources to load. Javascripts take 438.3 kB which makes up the majority of the site volume.
Potential reduce by 30.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 30.1 kB or 79% of the original size.
Potential reduce by 15.4 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. Nealepetersen images are well optimized though.
Potential reduce by 276.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 276.0 kB or 63% of the original size.
Potential reduce by 348.3 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. Nealepetersen.com needs all CSS files to be minified and compressed as it can save up to 348.3 kB or 84% of the original size.
Number of requests can be reduced by 24 (51%)
47
23
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nealepetersen. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
nealepetersen.com
2024 ms
style.css
581 ms
css
25 ms
css
37 ms
styles.css
568 ms
jetpack.css
596 ms
jquery.js
890 ms
jquery-migrate.min.js
601 ms
jquery.form.min.js
586 ms
scripts.js
849 ms
devicepx-jetpack.js
3 ms
gprofiles.js
53 ms
wpgroho.js
922 ms
jquery.flexslider.min.js
878 ms
custom.modernizr.min.js
871 ms
foundation.custom.min.js
921 ms
touchtouch.jquery.min.js
1119 ms
tinynav.min.js
1145 ms
site.js
1185 ms
e-201611.js
4 ms
event_intro.jpg
841 ms
Investor-Breakfast-20111-140x95.jpg
317 ms
Real-Estate-Investor-of-the-Year-140x95.jpg
316 ms
Jack-WelchJT-Foxx-Mega-Partnering1-140x95.jpg
511 ms
Wealth-Master-Class-Sandton-20132-140x95.jpg
529 ms
rode-reim1-140x95.jpg
559 ms
rode-reim2-140x95.jpg
569 ms
Neale-Robert-Kiyosaki-140x95.jpg
574 ms
Neale-and-Dolf1-140x95.jpg
782 ms
Bob-ProctorNeale-Petersen-140x95.jpg
820 ms
reim_banner.jpg
1128 ms
neale_personal_mailing1.jpg
1131 ms
analytics.js
8 ms
8B3H65_VrT0
112 ms
border_seperator.png
853 ms
bg_banner_6.jpg
1876 ms
sprite.png
1112 ms
border.gif
1150 ms
sprite_social_element.png
1147 ms
collect
19 ms
3igPYHysOQSqw-Nqzu4SMvesZW2xOQ-xsNqO47m55DA.woff
10 ms
ZvcMqxEwPfh2qDWBPxn6nmFp2sMiApZm5Dx7NpSTOZk.woff
10 ms
RFda8w1V0eDZheqfcyQ4EHhCUOGz7vYGh680lGh-uXM.woff
10 ms
www-embed-player-vflfNyN_r.css
23 ms
www-embed-player.js
34 ms
Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js
30 ms
ad_status.js
32 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
26 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
29 ms
g.gif
36 ms
hovercard.css
28 ms
services.css
52 ms
bg_quote.png
1097 ms
nealepetersen.com SEO score
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nealepetersen.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Nealepetersen.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.
nealepetersen.com
Open Graph description is not detected on the main page of Nealepetersen. 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: