Tools & Wizards About Us
postfunny.com screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    55% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

postfunny.com

postfunny.com- Free Fun Personality Quizzes & Photo Frames & More

Page Load Speed

2 sec in total

First Response

110 ms

Resources Loaded

445 ms

Page Rendered

1.4 sec

postfunny.com screenshot

About Website

Welcome to postfunny.com homepage info - get ready to check Post Fun Ny best content right away, or after learning these important things about postfunny.com

Relationship tests, personality analysis, IQ/EQ quizzes, fun tests.

Visit postfunny.com

Key Findings

We analyzed Postfunny.com page load time and found that the first response time was 110 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 40% of websites can load faster.

Performance Metrics

postfunny.com performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

79/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

54/100

25%

SI (Speed Index)

Value4.4 s

73/100

10%

TBT (Total Blocking Time)

Value1,400 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.871

4/100

15%

TTI (Time to Interactive)

Value11.3 s

19/100

10%

Network Requests Diagram

postfunny.com

110 ms

js

67 ms

swiper.css

103 ms

common.css

98 ms

adsbygoogle.js

248 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 79% of them (22 requests) were addressed to the original Postfunny.com, 7% (2 requests) were made to Connect.facebook.net and 4% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (248 ms) relates to the external source Pagead2.googlesyndication.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 101.3 kB (28%)

Content Size

364.2 kB

After Optimization

262.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-81%

Potential reduce by 45.4 kB

  • Original 56.0 kB
  • After minification 56.0 kB
  • After compression 10.6 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.4 kB or 81% of the original size.

Image Optimization

-50%

Potential reduce by 54.8 kB

  • Original 110.4 kB
  • After minification 55.6 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, Post Fun Ny needs image optimization as it can save up to 54.8 kB or 50% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 185.1 kB
  • After minification 185.1 kB
  • After compression 185.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. This website has mostly compressed JavaScripts.

CSS Optimization

-8%

Potential reduce by 1.0 kB

  • Original 12.8 kB
  • After minification 12.8 kB
  • After compression 11.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. Postfunny.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 11 (41%)

Requests Now

27

After Optimization

16

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

postfunny.com

postfunny.com

110 ms

js

js

67 ms

swiper.css

swiper.css

103 ms

common.css

common.css

98 ms

adsbygoogle.js

adsbygoogle.js

248 ms

config.js

config.js

65 ms

platform.js

platform.js

40 ms

jquery.min.js

jquery.min.js

100 ms

pub-1604387752354120

pub-1604387752354120

96 ms

email-decode.min.js

email-decode.min.js

4 ms

clipboard.min.js

clipboard.min.js

72 ms

index.js

index.js

99 ms

swiper.js

swiper.js

220 ms

sdk.js

sdk.js

134 ms

home_tab_logo.png

home_tab_logo.png

132 ms

icon_pic_topic.png

icon_pic_topic.png

123 ms

icon_search_pic.png

icon_search_pic.png

132 ms

icon_pic_close.png

icon_pic_close.png

132 ms

tab_icon_search.png

tab_icon_search.png

124 ms

icon_hot_fill.png

icon_hot_fill.png

183 ms

home_pic_circular.png

home_pic_circular.png

182 ms

pic_logo_Floorplan.png

pic_logo_Floorplan.png

185 ms

icon_arrow_direction.png

icon_arrow_direction.png

182 ms

en_label_icon_new.png

en_label_icon_new.png

181 ms

PC_staytuned_figure.png

PC_staytuned_figure.png

181 ms

PC_staytuned_success.png

PC_staytuned_success.png

206 ms

PC_staytuned_picture.png

PC_staytuned_picture.png

184 ms

sdk.js

sdk.js

10 ms

Accessibility Review

postfunny.com accessibility score

60

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

postfunny.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

postfunny.com SEO score

92

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

postfunny.com

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