Tools & Wizards About Us
verysimple.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

verysimple.com

Page Load Speed

1.2 sec in total

First Response

79 ms

Resources Loaded

885 ms

Page Rendered

265 ms

verysimple.com screenshot

About Website

Visit verysimple.com now to see the best up-to-date Verysimple content for United States and also check out these interesting facts you probably never knew about verysimple.com

VerySimple Custom Software Development and Personal Blog for Jason Hinkle

Visit verysimple.com

Key Findings

We analyzed Verysimple.com page load time and found that the first response time was 79 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

verysimple.com performance score

0

Network Requests Diagram

verysimple.com

79 ms

wp-emoji-release.min.js

16 ms

wp-syntax.css

26 ms

framework.css

40 ms

components.css

27 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 72% of them (21 requests) were addressed to the original Verysimple.com, 10% (3 requests) were made to I1.wp.com and 3% (1 request) were made to S0.wp.com. The less responsive or slowest element that took the longest time to load (691 ms) relates to the external source I1.wp.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 419.1 kB (69%)

Content Size

611.8 kB

After Optimization

192.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Verysimple.com main page is 611.8 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. 30% of websites need less resources to load. Javascripts take 325.8 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 25.4 kB

  • Original 31.7 kB
  • After minification 27.4 kB
  • After compression 6.3 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 4.3 kB, which is 14% 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 25.4 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 7 B

  • Original 88.9 kB
  • After minification 88.9 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. Verysimple images are well optimized though.

JavaScript Optimization

-77%

Potential reduce by 251.0 kB

  • Original 325.8 kB
  • After minification 253.3 kB
  • After compression 74.7 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 251.0 kB or 77% of the original size.

CSS Optimization

-86%

Potential reduce by 142.6 kB

  • Original 165.3 kB
  • After minification 112.4 kB
  • After compression 22.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. Verysimple.com needs all CSS files to be minified and compressed as it can save up to 142.6 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (68%)

Requests Now

28

After Optimization

9

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Verysimple. 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 10 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

verysimple.com

verysimple.com

79 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

16 ms

wp-syntax.css

wp-syntax.css

26 ms

framework.css

framework.css

40 ms

components.css

components.css

27 ms

responsive.css

responsive.css

75 ms

layers-icons.css

layers-icons.css

38 ms

style.css

style.css

54 ms

jetpack.css

jetpack.css

78 ms

jquery.js

jquery.js

58 ms

jquery-migrate.min.js

jquery-migrate.min.js

50 ms

plugins.js

plugins.js

56 ms

swiper.css

swiper.css

121 ms

inline.css

inline.css

118 ms

custom.css

custom.css

66 ms

photon.js

photon.js

68 ms

devicepx-jetpack.js

devicepx-jetpack.js

56 ms

layers.framework.js

layers.framework.js

119 ms

comment-reply.min.js

comment-reply.min.js

119 ms

wp-embed.min.js

wp-embed.min.js

162 ms

swiper.js

swiper.js

166 ms

e-201609.js

e-201609.js

4 ms

logo_final_cleaned.png

logo_final_cleaned.png

58 ms

logo-plugins.png

logo-plugins.png

190 ms

logo-blog.png

logo-blog.png

190 ms

logo_final_cleaned.png

logo_final_cleaned.png

691 ms

logo-open-source.png

logo-open-source.png

51 ms

layers-icons.woff

layers-icons.woff

132 ms

g.gif

g.gif

7 ms

SEO Factors

verysimple.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

Social Sharing Optimization

verysimple.com

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