Tools & Wizards About Us
fcode.ru screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

fcode.ru

Page Load Speed

3.7 sec in total

First Response

368 ms

Resources Loaded

3.1 sec

Page Rendered

251 ms

fcode.ru screenshot

About Website

Welcome to fcode.ru homepage info - get ready to check Fcode best content for Russia right away, or after learning these important things about fcode.ru

F.Code Butik – это не просто интернет-магазин брендовой одежды и аксессуаров класса люкс. Это – уникальный в своем роде интернет – магазин и аутлет, который работает в соответствии с европейскими стан...

Visit fcode.ru

Key Findings

We analyzed Fcode.ru page load time and found that the first response time was 368 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

fcode.ru performance score

0

Network Requests Diagram

fcode.ru

368 ms

www.fcode.ru

523 ms

insales_counter.js

136 ms

css

28 ms

style.css

296 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 6% of them (4 requests) were addressed to the original Fcode.ru, 40% (28 requests) were made to Assets3.insales.ru and 14% (10 requests) were made to Vk.com. The less responsive or slowest element that took the longest time to load (946 ms) relates to the external source Vk.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 373.8 kB (49%)

Content Size

763.9 kB

After Optimization

390.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fcode.ru main page is 763.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. 60% of websites need less resources to load. Javascripts take 336.3 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 47.8 kB

  • Original 63.7 kB
  • After minification 57.6 kB
  • After compression 15.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 47.8 kB or 75% of the original size.

Image Optimization

-11%

Potential reduce by 30.6 kB

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

JavaScript Optimization

-70%

Potential reduce by 236.7 kB

  • Original 336.3 kB
  • After minification 274.1 kB
  • After compression 99.7 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 236.7 kB or 70% of the original size.

CSS Optimization

-80%

Potential reduce by 58.7 kB

  • Original 73.6 kB
  • After minification 61.3 kB
  • After compression 14.9 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. Fcode.ru needs all CSS files to be minified and compressed as it can save up to 58.7 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (62%)

Requests Now

65

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fcode.ru

fcode.ru

368 ms

www.fcode.ru

www.fcode.ru

523 ms

insales_counter.js

insales_counter.js

136 ms

css

css

28 ms

style.css

style.css

296 ms

jquery.jscrollpane.css

jquery.jscrollpane.css

300 ms

jquery.rating.css

jquery.rating.css

295 ms

magiczoomplus.css

magiczoomplus.css

291 ms

jquery.js

jquery.js

32 ms

common_ru.js

common_ru.js

136 ms

common.js

common.js

293 ms

magiczoomplus.js

magiczoomplus.js

401 ms

cufon-yui.js

cufon-yui.js

417 ms

PT_Sans_Serif_400.font.js

PT_Sans_Serif_400.font.js

426 ms

jquery.mousewheel.js

jquery.mousewheel.js

423 ms

jquery.jscrollpane.min.js

jquery.jscrollpane.min.js

425 ms

fcode.js

fcode.js

423 ms

openapi.js

openapi.js

373 ms

share.js

share.js

496 ms

215

215

168 ms

widget.js

widget.js

450 ms

watch.js

watch.js

181 ms

counter.insales.ru

counter.insales.ru

349 ms

watch.js

watch.js

452 ms

widget_ru_RU.js

widget_ru_RU.js

286 ms

logo.gif

logo.gif

138 ms

Banner_big_201113_3.jpg

Banner_big_201113_3.jpg

769 ms

fb.gif

fb.gif

160 ms

tw.gif

tw.gif

160 ms

vk.gif

vk.gif

158 ms

foot_logo.png

foot_logo.png

153 ms

close.png

close.png

152 ms

sizes.png

sizes.png

328 ms

bottom.gif

bottom.gif

327 ms

woman.png

woman.png

326 ms

top.gif

top.gif

327 ms

man.png

man.png

326 ms

Banner_small_201113_1.jpg

Banner_small_201113_1.jpg

508 ms

Banner_small_201113_2.jpg

Banner_small_201113_2.jpg

492 ms

Banner_small_201113_3.jpg

Banner_small_201113_3.jpg

401 ms

ga.js

ga.js

29 ms

all.js

all.js

31 ms

v_dotted.gif

v_dotted.gif

296 ms

login.gif

login.gif

426 ms

search.gif

search.gif

426 ms

subscribe.gif

subscribe.gif

426 ms

arrow1.gif

arrow1.gif

426 ms

__utm.gif

__utm.gif

50 ms

UyYrYy3ltEffJV9QueSi4aUdwd0g3YZvPtKezrP11hs.ttf

UyYrYy3ltEffJV9QueSi4aUdwd0g3YZvPtKezrP11hs.ttf

147 ms

216 ms

p_methods.gif

p_methods.gif

312 ms

xd_arbiter.php

xd_arbiter.php

168 ms

xd_arbiter.php

xd_arbiter.php

185 ms

upload.gif

upload.gif

283 ms

widget_like.php

widget_like.php

422 ms

hit

hit

284 ms

advert.gif

advert.gif

195 ms

like.php

like.php

78 ms

bB7i3ZJb3iE.js

bB7i3ZJb3iE.js

43 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

28 ms

hit

hit

141 ms

1

1

88 ms

loader_nav19188_3.js

loader_nav19188_3.js

122 ms

lite.css

lite.css

240 ms

lite.js

lite.js

475 ms

lang3_0.js

lang3_0.js

243 ms

widgets.css

widgets.css

502 ms

xdm.js

xdm.js

946 ms

al_like.js

al_like.js

244 ms

like_widget.png

like_widget.png

119 ms

SEO Factors

fcode.ru SEO score

0

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fcode.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian 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 Fcode.ru 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

fcode.ru

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