Tools & Wizards About Us
creation.net screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

creation.net

:: Channy's Blog

Page Load Speed

11.8 sec in total

First Response

1.8 sec

Resources Loaded

9.1 sec

Page Rendered

867 ms

creation.net screenshot

About Website

Visit creation.net now to see the best up-to-date Creation content for South Korea and also check out these interesting facts you probably never knew about creation.net

Visit creation.net

Key Findings

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

Performance Metrics

creation.net performance score

0

Network Requests Diagram

channy.creation.net

1770 ms

bootstrap.css

19 ms

jquery.min.js

95 ms

bootstrap.min.js

46 ms

style.css

301 ms

Our browser made a total of 118 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Creation.net, 12% (14 requests) were made to Channy.creation.net and 8% (9 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source External.xx.fbcdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (47%)

Content Size

2.2 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Creation.net main page is 2.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 968.0 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 74.4 kB

  • Original 103.2 kB
  • After minification 100.9 kB
  • After compression 28.8 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 74.4 kB or 72% of the original size.

Image Optimization

-12%

Potential reduce by 113.5 kB

  • Original 968.0 kB
  • After minification 854.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, Creation needs image optimization as it can save up to 113.5 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-72%

Potential reduce by 681.6 kB

  • Original 946.4 kB
  • After minification 946.4 kB
  • After compression 264.8 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 681.6 kB or 72% of the original size.

CSS Optimization

-80%

Potential reduce by 170.6 kB

  • Original 214.6 kB
  • After minification 184.7 kB
  • After compression 44.0 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. Creation.net needs all CSS files to be minified and compressed as it can save up to 170.6 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 63 (57%)

Requests Now

111

After Optimization

48

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

channy.creation.net

channy.creation.net

1770 ms

bootstrap.css

bootstrap.css

19 ms

jquery.min.js

jquery.min.js

95 ms

bootstrap.min.js

bootstrap.min.js

46 ms

style.css

style.css

301 ms

genericons.css

genericons.css

472 ms

kind-style.css

kind-style.css

312 ms

wp-syntax.css

wp-syntax.css

336 ms

wps-seo-booster-front.css

wps-seo-booster-front.css

336 ms

addthis_widget.js

addthis_widget.js

16 ms

wp-embed.min.js

wp-embed.min.js

262 ms

aws-sdk.min.js

aws-sdk.min.js

1836 ms

aws-sdk-mobile-analytics.min.js

aws-sdk-mobile-analytics.min.js

569 ms

jsapi

jsapi

214 ms

channy

channy

204 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

409 ms

rss.svg

rss.svg

38 ms

32x32.png

32x32.png

328 ms

channy_1452270706_76.jpg

channy_1452270706_76.jpg

371 ms

facebook.svg

facebook.svg

101 ms

110x32bubble_b_ko.png

110x32bubble_b_ko.png

561 ms

btn_donate_SM.gif

btn_donate_SM.gif

208 ms

channy-bg.png

channy-bg.png

492 ms

channy-profile.png

channy-profile.png

1783 ms

github.png

github.png

204 ms

indiewebcamp.png

indiewebcamp.png

344 ms

twitter.svg

twitter.svg

99 ms

linkedin.svg

linkedin.svg

108 ms

google_follow.svg

google_follow.svg

102 ms

youtube.svg

youtube.svg

103 ms

32x32.png

32x32.png

294 ms

32x32.png

32x32.png

295 ms

32x32.png

32x32.png

297 ms

32x32.png

32x32.png

297 ms

32x32.png

32x32.png

299 ms

32x32.png

32x32.png

299 ms

32x32.png

32x32.png

309 ms

NotoSansKR-Bold-subset.woff

NotoSansKR-Bold-subset.woff

376 ms

NotoSansKR-Light-subset.woff

NotoSansKR-Light-subset.woff

392 ms

widgets.js

widgets.js

99 ms

ga.js

ga.js

102 ms

likebox.php

likebox.php

333 ms

__utm.gif

__utm.gif

28 ms

collect

collect

59 ms

NotoSansKR-Bold-subset.otf

NotoSansKR-Bold-subset.otf

174 ms

NotoSansKR-Light-subset.otf

NotoSansKR-Light-subset.otf

213 ms

kyEKgjk51ZE.css

kyEKgjk51ZE.css

137 ms

kTub4bakEmM.css

kTub4bakEmM.css

149 ms

Czh0gDTFcBt.css

Czh0gDTFcBt.css

223 ms

N-k91nHCZS2.css

N-k91nHCZS2.css

245 ms

ZeuPykSxSED.css

ZeuPykSxSED.css

268 ms

FAHeNGXgPup.js

FAHeNGXgPup.js

262 ms

FJmpeSpHpjS.js

FJmpeSpHpjS.js

378 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

241 ms

1bNoFZUdlYZ.js

1bNoFZUdlYZ.js

237 ms

njO1TPvGzoR.js

njO1TPvGzoR.js

373 ms

1QuX41zDRrx.js

1QuX41zDRrx.js

376 ms

Oagsvfb4VWi.js

Oagsvfb4VWi.js

424 ms

m-2AbGY1fWh.js

m-2AbGY1fWh.js

438 ms

1FCa-btixu2.js

1FCa-btixu2.js

435 ms

11737920_948931865171616_6594871874629709402_n.jpg

11737920_948931865171616_6594871874629709402_n.jpg

706 ms

safe_image.php

safe_image.php

2984 ms

safe_image.php

safe_image.php

3148 ms

safe_image.php

safe_image.php

3133 ms

535232_1032945526770249_887385010668324617_n.jpg

535232_1032945526770249_887385010668324617_n.jpg

2927 ms

11083860_1563386977251331_4494546558722672312_n.jpg

11083860_1563386977251331_4494546558722672312_n.jpg

2926 ms

12806261_10156695557975235_4416761612622579080_n.jpg

12806261_10156695557975235_4416761612622579080_n.jpg

2925 ms

12246662_1066607330070735_3084633573883311897_n.jpg

12246662_1066607330070735_3084633573883311897_n.jpg

2926 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

388 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

389 ms

QDwYpIaRyfG.png

QDwYpIaRyfG.png

388 ms

sSwLTfB7PfP.png

sSwLTfB7PfP.png

387 ms

K00K-UgnsKu.png

K00K-UgnsKu.png

385 ms

254 ms

default+en.css

default+en.css

12 ms

default+en.I.js

default+en.I.js

2287 ms

boost

boost

57 ms

300lo.json

300lo.json

48 ms

all.js&version=v2.0

all.js&version=v2.0

464 ms

plusone.js

plusone.js

142 ms

counter.5524cceca805eb4b9b2b.js

counter.5524cceca805eb4b9b2b.js

104 ms

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

133 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

135 ms

sh.07f0d9bf220d07a763adad1e.html

sh.07f0d9bf220d07a763adad1e.html

91 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

113 ms

pQrUxxo5oQp.js

pQrUxxo5oQp.js

113 ms

shares.json

shares.json

91 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

155 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

212 ms

fastbutton

fastbutton

288 ms

syndication

syndication

245 ms

432146758768926722

432146758768926722

503 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ko.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ko.html

34 ms

jot

jot

80 ms

postmessageRelay

postmessageRelay

141 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

99 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

99 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

96 ms

50 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

89 ms

rpc:shindig_random.js

rpc:shindig_random.js

43 ms

xd_arbiter.php

xd_arbiter.php

80 ms

xd_arbiter.php

xd_arbiter.php

158 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

13 ms

25b6.png

25b6.png

38 ms

proxy.jpg

proxy.jpg

430 ms

proxy.jpg

proxy.jpg

421 ms

Gfeeds

Gfeeds

408 ms

ping

ping

62 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

4 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

7 ms

JtQdGL-3_normal.jpg

JtQdGL-3_normal.jpg

374 ms

2472f07f137172086f4f4594fe7f3c40_normal.png

2472f07f137172086f4f4594fe7f3c40_normal.png

380 ms

syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css

syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css

48 ms

syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css

syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css

183 ms

like.php

like.php

219 ms

U9rHIpG5ERY.js

U9rHIpG5ERY.js

128 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

19 ms

SEO Factors

creation.net SEO score

0

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 Creation.net 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 Creation.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

creation.net

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