Tools & Wizards About Us
creative.su screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

creative.su

Творческий портал Creative.SU : Общий поток

Page Load Speed

5.1 sec in total

First Response

744 ms

Resources Loaded

2.7 sec

Page Rendered

1.6 sec

creative.su screenshot

About Website

Visit creative.su now to see the best up-to-date Creative content for Russia and also check out these interesting facts you probably never knew about creative.su

Visit creative.su

Key Findings

We analyzed Creative.su page load time and found that the first response time was 744 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

creative.su performance score

0

Network Requests Diagram

creative.su

744 ms

wakka.css

382 ms

adipoli.css

385 ms

cities.css

386 ms

jquery-1.4.2.min.js

910 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 79% of them (62 requests) were addressed to the original Creative.su, 5% (4 requests) were made to Mc.yandex.ru and 5% (4 requests) were made to Acint.net. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Creative.su.

Page Optimization Overview & Recommendations

Page size can be reduced by 373.0 kB (46%)

Content Size

810.9 kB

After Optimization

437.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Creative.su main page is 810.9 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. 35% of websites need less resources to load. Images take 374.8 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 72.3 kB

  • Original 86.3 kB
  • After minification 78.3 kB
  • After compression 13.9 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 72.3 kB or 84% of the original size.

Image Optimization

-18%

Potential reduce by 66.3 kB

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

JavaScript Optimization

-66%

Potential reduce by 213.2 kB

  • Original 322.4 kB
  • After minification 293.4 kB
  • After compression 109.1 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 213.2 kB or 66% of the original size.

CSS Optimization

-77%

Potential reduce by 21.2 kB

  • Original 27.4 kB
  • After minification 20.0 kB
  • After compression 6.3 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. Creative.su needs all CSS files to be minified and compressed as it can save up to 21.2 kB or 77% of the original size.

Requests Breakdown

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

Requests Now

73

After Optimization

40

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

creative.su

creative.su

744 ms

wakka.css

wakka.css

382 ms

adipoli.css

adipoli.css

385 ms

cities.css

cities.css

386 ms

jquery-1.4.2.min.js

jquery-1.4.2.min.js

910 ms

jquery.adipoli.min.js

jquery.adipoli.min.js

650 ms

jq.wrapcaptions.js

jq.wrapcaptions.js

391 ms

default.js

default.js

625 ms

protoedit.js

protoedit.js

628 ms

wikiedit2.js

wikiedit2.js

755 ms

JsHttpRequest.js

JsHttpRequest.js

653 ms

JsHttpRequest_QuickStart.js.version3

JsHttpRequest_QuickStart.js.version3

749 ms

lock2.js

lock2.js

1027 ms

calendar.js

calendar.js

782 ms

calendar-blue.css

calendar-blue.css

378 ms

calendar_stripped.js

calendar_stripped.js

624 ms

calendar-ru_win_.js

calendar-ru_win_.js

377 ms

calendar-setup_stripped.js

calendar-setup_stripped.js

390 ms

top100.jcn

top100.jcn

379 ms

watch.js

watch.js

182 ms

reset.css

reset.css

499 ms

grid12.css

grid12.css

503 ms

text.css

text.css

531 ms

text2.css

text2.css

538 ms

wakka.css

wakka.css

620 ms

watch.js

watch.js

489 ms

0.gif

0.gif

206 ms

svetlovka.gif

svetlovka.gif

481 ms

logo.png

logo.png

523 ms

lumelu-unreg.png

lumelu-unreg.png

500 ms

goldenimg.php

goldenimg.php

316 ms

goldenimg.php

goldenimg.php

344 ms

goldenimg.php

goldenimg.php

379 ms

Lit-kuhnya-2009.png

Lit-kuhnya-2009.png

376 ms

strelka_vniz.png

strelka_vniz.png

424 ms

bg.png

bg.png

199 ms

process.gif

process.gif

192 ms

menu_obsh.png

menu_obsh.png

198 ms

menu_risu.png

menu_risu.png

193 ms

menu_proz.png

menu_proz.png

195 ms

menu_stih.png

menu_stih.png

197 ms

menu_muzi.png

menu_muzi.png

272 ms

menu_foto.png

menu_foto.png

274 ms

menu_forum.png

menu_forum.png

274 ms

menu_novo.png

menu_novo.png

277 ms

gold-pentacle.png

gold-pentacle.png

274 ms

z.gif

z.gif

275 ms

1455566410_48634_p1.jpg

1455566410_48634_p1.jpg

369 ms

1438583103_25039_p1.jpg

1438583103_25039_p1.jpg

374 ms

1457407664_40861_p1.jpg

1457407664_40861_p1.jpg

373 ms

647678860_49949_p2.jpg

647678860_49949_p2.jpg

393 ms

pentacle1.png

pentacle1.png

393 ms

1457043165_96785_p1.jpg

1457043165_96785_p1.jpg

394 ms

p1011092_49948_p2.jpg

p1011092_49948_p2.jpg

638 ms

p1011110_49947_p2.jpg

p1011110_49947_p2.jpg

639 ms

1446899704_47125_p1.jpg

1446899704_47125_p1.jpg

515 ms

1332193019_32707_p1.jpg

1332193019_32707_p1.jpg

520 ms

001122_49946_p2.jpg

001122_49946_p2.jpg

648 ms

1448387898_83538_p1.jpg

1448387898_83538_p1.jpg

520 ms

povarjeto_49945_p2.jpg

povarjeto_49945_p2.jpg

760 ms

1457780684_67089_p1.jpg

1457780684_67089_p1.jpg

647 ms

cvetik_49944_p2.jpg

cvetik_49944_p2.jpg

775 ms

fizteh.gif

fizteh.gif

756 ms

stm-banner.gif

stm-banner.gif

751 ms

top100.scn

top100.scn

159 ms

gold-tb-top.png

gold-tb-top.png

1075 ms

gold-tb-bottom.png

gold-tb-bottom.png

686 ms

aci.js

aci.js

188 ms

ga.js

ga.js

27 ms

hit

hit

263 ms

__utm.gif

__utm.gif

40 ms

advert.gif

advert.gif

97 ms

96 ms

186 ms

404.html

404.html

398 ms

1

1

92 ms

255 ms

match

match

192 ms

SEO Factors

creative.su SEO score

0

Language and Encoding

  • Language Detected

    SR

  • Language Claimed

    N/A

  • Encoding

    WINDOWS-1251

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Creative.su can be misinterpreted by Google and other search engines. Our service has detected that Serbian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Creative.su main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

creative.su

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