Tools & Wizards About Us
johnlavenia.net screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

johnlavenia.net

Home Page - John Lavenia

Page Load Speed

3.6 sec in total

First Response

795 ms

Resources Loaded

2.2 sec

Page Rendered

637 ms

johnlavenia.net screenshot

About Website

Welcome to johnlavenia.net homepage info - get ready to check John Lavenia best content right away, or after learning these important things about johnlavenia.net

The official blog of author, speaker and marketing mentor John Lavenia. Marketing tips and advice for business owners motivated to expand their business.

Visit johnlavenia.net

Key Findings

We analyzed Johnlavenia.net page load time and found that the first response time was 795 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

johnlavenia.net performance score

0

Network Requests Diagram

www.johnlavenia.net

795 ms

common.css

21 ms

common-base.css

17 ms

jqueryUi.css

24 ms

colorpicker.css

29 ms

Our browser made a total of 107 requests to load all elements on the main page. We found that 36% of them (39 requests) were addressed to the original Johnlavenia.net, 25% (27 requests) were made to Legacyblog.empowernetwork.com and 13% (14 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (795 ms) belongs to the original domain Johnlavenia.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 998.9 kB (56%)

Content Size

1.8 MB

After Optimization

798.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Johnlavenia.net main page is 1.8 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. 80% 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 921.7 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 46.2 kB

  • Original 59.4 kB
  • After minification 55.5 kB
  • After compression 13.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. 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 46.2 kB or 78% of the original size.

Image Optimization

-36%

Potential reduce by 328.4 kB

  • Original 921.7 kB
  • After minification 593.3 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. Obviously, John Lavenia needs image optimization as it can save up to 328.4 kB or 36% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-62%

Potential reduce by 172.6 kB

  • Original 277.8 kB
  • After minification 277.7 kB
  • After compression 105.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 172.6 kB or 62% of the original size.

CSS Optimization

-84%

Potential reduce by 451.7 kB

  • Original 538.1 kB
  • After minification 484.7 kB
  • After compression 86.4 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. Johnlavenia.net needs all CSS files to be minified and compressed as it can save up to 451.7 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 66 (66%)

Requests Now

100

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 100 CSS, Javascripts, AJAX and image requests in order to completely render the main page of John Lavenia. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.johnlavenia.net

www.johnlavenia.net

795 ms

common.css

common.css

21 ms

common-base.css

common-base.css

17 ms

jqueryUi.css

jqueryUi.css

24 ms

colorpicker.css

colorpicker.css

29 ms

colorbox.css

colorbox.css

28 ms

prettyCheckboxes.css

prettyCheckboxes.css

29 ms

dd.css

dd.css

30 ms

jscrollpane.css

jscrollpane.css

31 ms

stream.css

stream.css

31 ms

instant-login.css

instant-login.css

38 ms

blog.css

blog.css

39 ms

modernizr.js

modernizr.js

44 ms

jquery.1.9.1.js

jquery.1.9.1.js

51 ms

jqueryMigrate.js

jqueryMigrate.js

44 ms

common.js

common.js

46 ms

common.js

common.js

44 ms

jqueryUi.js

jqueryUi.js

48 ms

jquery.typing-0.2.0.min.js

jquery.typing-0.2.0.min.js

46 ms

colorpicker.js

colorpicker.js

45 ms

colorbox.js

colorbox.js

48 ms

dd.js

dd.js

48 ms

prettyCheckboxes.js

prettyCheckboxes.js

49 ms

jscrollpane.js

jscrollpane.js

50 ms

mousewheel.js

mousewheel.js

52 ms

mwheelIntent.js

mwheelIntent.js

51 ms

validation.js

validation.js

56 ms

validation.bootstrap.js

validation.bootstrap.js

55 ms

autosize.js

autosize.js

55 ms

viewPostClass.js

viewPostClass.js

56 ms

comment.js

comment.js

59 ms

responsiveslides.min.js

responsiveslides.min.js

56 ms

timeago.js

timeago.js

62 ms

blog.js

blog.js

66 ms

plusone.js

plusone.js

56 ms

@importColor.css

@importColor.css

62 ms

@importTypography.css

@importTypography.css

62 ms

@importMargin.css

@importMargin.css

62 ms

@importPadding.css

@importPadding.css

67 ms

@importWidth.css

@importWidth.css

65 ms

@importHeight.css

@importHeight.css

69 ms

@importLayout.css

@importLayout.css

70 ms

@importForm.css

@importForm.css

73 ms

jquery.countdown.css

jquery.countdown.css

30 ms

print.css

print.css

5 ms

pageTopBg.png

pageTopBg.png

209 ms

gtm.js

gtm.js

148 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

170 ms

960x265_20140410_c1b64e7ac223613d4c06021db35325b7_png.png

960x265_20140410_c1b64e7ac223613d4c06021db35325b7_png.png

581 ms

analytics.js

analytics.js

205 ms

widgets.js

widgets.js

92 ms

plusone.js

plusone.js

163 ms

load-menu

load-menu

367 ms

load-categories

load-categories

434 ms

load-recent-post

load-recent-post

358 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

144 ms

fastbutton

fastbutton

230 ms

fastbutton

fastbutton

232 ms

fastbutton

fastbutton

226 ms

fastbutton

fastbutton

226 ms

fastbutton

fastbutton

223 ms

172x172_20131011_3fa8ba50ecb239184090120600c6e3bb_png.png

172x172_20131011_3fa8ba50ecb239184090120600c6e3bb_png.png

222 ms

540x293_20140709_6c19920d0d9b4d0581f3c952e6f1f9c9_JPG.JPG

540x293_20140709_6c19920d0d9b4d0581f3c952e6f1f9c9_JPG.JPG

230 ms

blueBtnBg.png

blueBtnBg.png

38 ms

customizerBlockBg.png

customizerBlockBg.png

57 ms

blogNavBg.jpg

blogNavBg.jpg

126 ms

commentBuble.png

commentBuble.png

57 ms

likesCount.png

likesCount.png

56 ms

likeCount.png

likeCount.png

54 ms

paginationBg.jpg

paginationBg.jpg

54 ms

greyBtnBg.png

greyBtnBg.png

205 ms

greyBtnBg.jpg

greyBtnBg.jpg

215 ms

rssFeedIcon.jpg

rssFeedIcon.jpg

216 ms

verisignIcons.jpg

verisignIcons.jpg

221 ms

312x555_blogBanner.jpg

312x555_blogBanner.jpg

222 ms

960x188_blogBanner.jpg

960x188_blogBanner.jpg

203 ms

droidsans-webfont.woff

droidsans-webfont.woff

54 ms

droidsans-bold-webfont.woff

droidsans-bold-webfont.woff

121 ms

PTbxXfy4-Cg

PTbxXfy4-Cg

312 ms

blog

blog

600 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

184 ms

collect

collect

202 ms

collect

collect

349 ms

postmessageRelay

postmessageRelay

293 ms

collect

collect

159 ms

rs=AGLTcCMZQMkD3nQb9neyXrDGlfp1IpCqrw

rs=AGLTcCMZQMkD3nQb9neyXrDGlfp1IpCqrw

30 ms

j1_CrSF7rmY

j1_CrSF7rmY

147 ms

qeJcTV5IAAM

qeJcTV5IAAM

250 ms

_rKZ7ugJ71U

_rKZ7ugJ71U

248 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

146 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

146 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

228 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

221 ms

www-embed-player.js

www-embed-player.js

249 ms

blogNavSeperator.jpg

blogNavSeperator.jpg

170 ms

selectBg.png

selectBg.png

111 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

62 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

56 ms

rpc:shindig_random.js

rpc:shindig_random.js

43 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

31 ms

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

85 ms

ad_status.js

ad_status.js

132 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

8 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

8 ms

nr-885.min.js

nr-885.min.js

17 ms

0013750a9b

0013750a9b

49 ms

jot.html

jot.html

3 ms

SEO Factors

johnlavenia.net SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Johnlavenia.net 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 Johnlavenia.net 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.

Social Sharing Optimization

johnlavenia.net

Open Graph description is not detected on the main page of John Lavenia. 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: