Tools & Wizards About Us
postly.co screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

postly.co

Postly

Page Load Speed

994 ms in total

First Response

28 ms

Resources Loaded

519 ms

Page Rendered

447 ms

postly.co screenshot

About Website

Visit postly.co now to see the best up-to-date Postly content for India and also check out these interesting facts you probably never knew about postly.co

Visit postly.co

Key Findings

We analyzed Postly.co page load time and found that the first response time was 28 ms and then it took 966 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

postly.co performance score

0

Network Requests Diagram

www.postly.co

28 ms

css

91 ms

bootstrap.css

16 ms

animate.css

71 ms

postly-web.css

43 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 88% of them (22 requests) were addressed to the original Postly.co, 4% (1 request) were made to Fonts.googleapis.com and 4% (1 request) were made to Static.getclicky.com. The less responsive or slowest element that took the longest time to load (281 ms) relates to the external source Static.getclicky.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 839.2 kB (26%)

Content Size

3.2 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Postly.co main page is 3.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. 75% 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 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 5.9 kB

  • Original 8.1 kB
  • After minification 6.4 kB
  • After compression 2.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. This page needs HTML code to be minified as it can gain 1.6 kB, which is 20% 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 5.9 kB or 74% of the original size.

Image Optimization

-19%

Potential reduce by 536.2 kB

  • Original 2.8 MB
  • After minification 2.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, Postly needs image optimization as it can save up to 536.2 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-65%

Potential reduce by 121.0 kB

  • Original 185.8 kB
  • After minification 185.1 kB
  • After compression 64.9 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 121.0 kB or 65% of the original size.

CSS Optimization

-89%

Potential reduce by 176.1 kB

  • Original 197.3 kB
  • After minification 160.3 kB
  • After compression 21.1 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. Postly.co needs all CSS files to be minified and compressed as it can save up to 176.1 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (33%)

Requests Now

24

After Optimization

16

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.postly.co

www.postly.co

28 ms

css

css

91 ms

bootstrap.css

bootstrap.css

16 ms

animate.css

animate.css

71 ms

postly-web.css

postly-web.css

43 ms

jquery.min.js

jquery.min.js

69 ms

bootstrap.min.js

bootstrap.min.js

40 ms

isInViewport.min.js

isInViewport.min.js

39 ms

postly-web.js

postly-web.js

45 ms

js

js

281 ms

logo.png

logo.png

45 ms

play.png

play.png

44 ms

app-store.png

app-store.png

45 ms

google-play.png

google-play.png

118 ms

macphone1.png

macphone1.png

123 ms

rnd-pencil.png

rnd-pencil.png

84 ms

rnd-photo.png

rnd-photo.png

82 ms

rnd-headphones.png

rnd-headphones.png

83 ms

rnd-link.png

rnd-link.png

82 ms

macphone2.png

macphone2.png

129 ms

macphone3.png

macphone3.png

129 ms

rnd-camera.png

rnd-camera.png

112 ms

rnd-location.png

rnd-location.png

111 ms

hero-img.png

hero-img.png

27 ms

analytics.js

analytics.js

6 ms

SEO Factors

postly.co SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Postly.co 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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Postly.co 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

postly.co

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