Tools & Wizards About Us
funnyplan.com screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    59% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

funnyplan.com

주식회사 동네서점

Page Load Speed

5.6 sec in total

First Response

537 ms

Resources Loaded

4.8 sec

Page Rendered

237 ms

funnyplan.com screenshot

About Website

Welcome to funnyplan.com homepage info - get ready to check Funnyplan best content for South Korea right away, or after learning these important things about funnyplan.com

Funnyplan creates funny smart web and app services. Our mission is to help connecting people and sharing inspirations with each other.

Visit funnyplan.com

Key Findings

We analyzed Funnyplan.com page load time and found that the first response time was 537 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

funnyplan.com performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

8/100

10%

LCP (Largest Contentful Paint)

Value22.6 s

0/100

25%

SI (Speed Index)

Value11.4 s

5/100

10%

TBT (Total Blocking Time)

Value320 ms

76/100

30%

CLS (Cumulative Layout Shift)

Value0.067

97/100

15%

TTI (Time to Interactive)

Value14.8 s

8/100

10%

Network Requests Diagram

www.funnyplan.com

537 ms

analytics.js

33 ms

wp-emoji-release.min.js

239 ms

gtranslate-style16.css

475 ms

style.css

477 ms

Our browser made a total of 118 requests to load all elements on the main page. We found that 16% of them (19 requests) were addressed to the original Funnyplan.com, 23% (27 requests) were made to Maps.googleapis.com and 21% (25 requests) were made to Mt.googleapis.com. The less responsive or slowest element that took the longest time to load (2.8 sec) relates to the external source I0.wp.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 680.9 kB (48%)

Content Size

1.4 MB

After Optimization

728.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-72%

Potential reduce by 21.0 kB

  • Original 29.4 kB
  • After minification 28.5 kB
  • After compression 8.4 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 21.0 kB or 72% of the original size.

Image Optimization

-3%

Potential reduce by 11.5 kB

  • Original 437.3 kB
  • After minification 425.8 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. Funnyplan images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 511.4 kB

  • Original 777.7 kB
  • After minification 773.7 kB
  • After compression 266.3 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 511.4 kB or 66% of the original size.

CSS Optimization

-83%

Potential reduce by 137.0 kB

  • Original 165.2 kB
  • After minification 150.1 kB
  • After compression 28.2 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. Funnyplan.com needs all CSS files to be minified and compressed as it can save up to 137.0 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 75 (69%)

Requests Now

108

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.funnyplan.com

www.funnyplan.com

537 ms

analytics.js

analytics.js

33 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

239 ms

gtranslate-style16.css

gtranslate-style16.css

475 ms

style.css

style.css

477 ms

css

css

40 ms

ionicons.min.css

ionicons.min.css

14 ms

bxslider.css

bxslider.css

472 ms

jetpack.css

jetpack.css

480 ms

jquery.js

jquery.js

716 ms

jquery-migrate.min.js

jquery-migrate.min.js

706 ms

skip-links.js

skip-links.js

704 ms

jquery.fitvids.js

jquery.fitvids.js

708 ms

global.js

global.js

709 ms

responsive-menu.js

responsive-menu.js

729 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

936 ms

all.js

all.js

164 ms

photon.js

photon.js

996 ms

devicepx-jetpack.js

devicepx-jetpack.js

14 ms

gprofiles.js

gprofiles.js

54 ms

wpgroho.js

wpgroho.js

997 ms

hoverIntent.min.js

hoverIntent.min.js

998 ms

superfish.min.js

superfish.min.js

997 ms

superfish.args.min.js

superfish.args.min.js

997 ms

wp-embed.min.js

wp-embed.min.js

1163 ms

e-201611.js

e-201611.js

26 ms

collect

collect

12 ms

%EC%96%B4%EC%84%9C%EC%98%A4%EC%84%B8%EC%98%A4%EB%8A%98%EC%9D%98%EB%8F%99%EB%84%A4%EC%84%9C%EC%A0%90-%EC%8A%A4%ED%86%A0%EB%A6%AC%ED%8E%80%EB%94%A9-%EB%A7%88%EA%B0%90.jpg

%EC%96%B4%EC%84%9C%EC%98%A4%EC%84%B8%EC%98%A4%EB%8A%98%EC%9D%98%EB%8F%99%EB%84%A4%EC%84%9C%EC%A0%90-%EC%8A%A4%ED%86%A0%EB%A6%AC%ED%8E%80%EB%94%A9-%EB%A7%88%EA%B0%90.jpg

2755 ms

Funnyplan_white_logo_1line-md-t.png

Funnyplan_white_logo_1line-md-t.png

477 ms

embed

embed

763 ms

mjitrc9VnL7D7tS-i3g3XQ.woff

mjitrc9VnL7D7tS-i3g3XQ.woff

11 ms

yATwQM0pIZXIFPrEDZyOHg.woff

yATwQM0pIZXIFPrEDZyOHg.woff

11 ms

R5nyNcvoz7n0iBHxjY_LyQ.woff

R5nyNcvoz7n0iBHxjY_LyQ.woff

11 ms

2dBELi3ZbivnVPt1KR2lhQ.woff

2dBELi3ZbivnVPt1KR2lhQ.woff

12 ms

lyIZFqDTaXXyAxN6-svvJg.woff

lyIZFqDTaXXyAxN6-svvJg.woff

11 ms

128 ms

xd_arbiter.php

xd_arbiter.php

136 ms

xd_arbiter.php

xd_arbiter.php

258 ms

hovercard.css

hovercard.css

27 ms

services.css

services.css

53 ms

ping

ping

60 ms

g.gif

g.gif

3 ms

like.php

like.php

92 ms

8i5wLKr4CIi.js

8i5wLKr4CIi.js

305 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

328 ms

rs=ABjfnFW3NcDEAUOJhqBLkb_g7tp8huHPRg

rs=ABjfnFW3NcDEAUOJhqBLkb_g7tp8huHPRg

44 ms

css

css

78 ms

js

js

76 ms

rs=ABjfnFVj2c6_lUpgxbr93j8J5XcedEcimw

rs=ABjfnFVj2c6_lUpgxbr93j8J5XcedEcimw

41 ms

d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff

d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff

212 ms

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

293 ms

2UX7WLTfW3W8TclTUvlFyQ.woff

2UX7WLTfW3W8TclTUvlFyQ.woff

351 ms

Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff

Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff

350 ms

rs=ABjfnFVj2c6_lUpgxbr93j8J5XcedEcimw

rs=ABjfnFVj2c6_lUpgxbr93j8J5XcedEcimw

101 ms

common.js

common.js

98 ms

map.js

map.js

110 ms

overlay.js

overlay.js

111 ms

1493-wht-blank_maps-4x.png&filter=ffDB4436&scale=1.0

1493-wht-blank_maps-4x.png&filter=ffDB4436&scale=1.0

226 ms

util.js

util.js

221 ms

marker.js

marker.js

169 ms

geocoder.js

geocoder.js

57 ms

controls.js

controls.js

173 ms

places_impl.js

places_impl.js

173 ms

979-biz-bar.png&filter=ff&scale=1.0

979-biz-bar.png&filter=ff&scale=1.0

264 ms

1259-poi-grain-mill.png&filter=ff&scale=1.0

1259-poi-grain-mill.png&filter=ff&scale=1.0

311 ms

1261-poi-historic-building.png&filter=ff&scale=1.0

1261-poi-historic-building.png&filter=ff&scale=1.0

310 ms

1341-poi-theater.png&filter=ff&scale=1.0

1341-poi-theater.png&filter=ff&scale=1.0

310 ms

991-biz-cafe.png&filter=ff&scale=1.0

991-biz-cafe.png&filter=ff&scale=1.0

333 ms

1239-poi-civic.png&filter=ff&scale=1.0

1239-poi-civic.png&filter=ff&scale=1.0

327 ms

1053-biz-music.png&filter=ff&scale=1.0

1053-biz-music.png&filter=ff&scale=1.0

331 ms

1107-biz-theater.png&filter=ff&scale=1.0

1107-biz-theater.png&filter=ff&scale=1.0

332 ms

1229-poi-art.png&filter=ff&scale=1.0

1229-poi-art.png&filter=ff&scale=1.0

331 ms

1125-crisis-caution.png&filter=ff&scale=1.0

1125-crisis-caution.png&filter=ff&scale=1.0

333 ms

1111-biz-travel.png&filter=ff&scale=1.0

1111-biz-travel.png&filter=ff&scale=1.0

334 ms

1035-biz-hotel.png&filter=ff&scale=1.0

1035-biz-hotel.png&filter=ff&scale=1.0

345 ms

selection_2x-000.png

selection_2x-000.png

36 ms

gen204

gen204

168 ms

onion.js

onion.js

105 ms

openhand_8_8.cur

openhand_8_8.cur

247 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

168 ms

stats.js

stats.js

140 ms

StaticMapService.GetMapImage

StaticMapService.GetMapImage

279 ms

transparent.png

transparent.png

94 ms

mapcnt6.png

mapcnt6.png

102 ms

tmapctrl4.png

tmapctrl4.png

85 ms

vt

vt

25 ms

vt

vt

22 ms

vt

vt

21 ms

vt

vt

51 ms

vt

vt

21 ms

vt

vt

60 ms

vt

vt

26 ms

vt

vt

26 ms

vt

vt

27 ms

vt

vt

63 ms

vt

vt

34 ms

vt

vt

52 ms

vt

vt

37 ms

viewer-icons001.png

viewer-icons001.png

119 ms

star4.png

star4.png

128 ms

979-biz-bar.png&scale=1.0

979-biz-bar.png&scale=1.0

115 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

67 ms

1259-poi-grain-mill.png&scale=1.0

1259-poi-grain-mill.png&scale=1.0

56 ms

1261-poi-historic-building.png&scale=1.0

1261-poi-historic-building.png&scale=1.0

56 ms

1341-poi-theater.png&scale=1.0

1341-poi-theater.png&scale=1.0

56 ms

991-biz-cafe.png&scale=1.0

991-biz-cafe.png&scale=1.0

56 ms

1239-poi-civic.png&scale=1.0

1239-poi-civic.png&scale=1.0

55 ms

1053-biz-music.png&scale=1.0

1053-biz-music.png&scale=1.0

61 ms

1107-biz-theater.png&scale=1.0

1107-biz-theater.png&scale=1.0

61 ms

1229-poi-art.png&scale=1.0

1229-poi-art.png&scale=1.0

61 ms

1125-crisis-caution.png&scale=1.0

1125-crisis-caution.png&scale=1.0

60 ms

1111-biz-travel.png&scale=1.0

1111-biz-travel.png&scale=1.0

66 ms

1035-biz-hotel.png&scale=1.0

1035-biz-hotel.png&scale=1.0

61 ms

MyMaps_Icons003.png

MyMaps_Icons003.png

49 ms

mymaps_32.png

mymaps_32.png

48 ms

v1_4593b7d7.png

v1_4593b7d7.png

60 ms

google-my-maps-logo-small-001.png

google-my-maps-logo-small-001.png

60 ms

kh

kh

63 ms

Accessibility Review

funnyplan.com accessibility score

100

Accessibility Issues

Best Practices

funnyplan.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

funnyplan.com SEO score

100

Search Engine Optimization Advices

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

    KO

  • Language Claimed

    KO

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Funnyplan.com can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and it matches the claimed language. Our system also found out that Funnyplan.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

funnyplan.com

Open Graph data is detected on the main page of Funnyplan. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: