Tools & Wizards About Us
forclock.ru screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

forclock.ru

Часы в кино

Page Load Speed

6.5 sec in total

First Response

1.4 sec

Resources Loaded

4.5 sec

Page Rendered

628 ms

forclock.ru screenshot

About Website

Visit forclock.ru now to see the best up-to-date Forclock content and also check out these interesting facts you probably never knew about forclock.ru

Сайт про часы в кино. Разбираемся, что носят актеры, ищем стоимость моделей и историю реквизита.

Visit forclock.ru

Key Findings

We analyzed Forclock.ru page load time and found that the first response time was 1.4 sec 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

forclock.ru performance score

0

Network Requests Diagram

forclock.ru

1437 ms

www.forclock.ru

311 ms

AC_RunActiveContent.js

299 ms

protoaculous1.6.packed.js

430 ms

highslide-full.js

792 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 92% of them (54 requests) were addressed to the original Forclock.ru, 3% (2 requests) were made to Counter.yadro.ru and 2% (1 request) were made to Yandex.st. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Forclock.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 402.3 kB (35%)

Content Size

1.1 MB

After Optimization

734.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Forclock.ru main page is 1.1 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. 30% of websites need less resources to load. Images take 781.5 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 69.6 kB

  • Original 81.4 kB
  • After minification 65.9 kB
  • After compression 11.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. This page needs HTML code to be minified as it can gain 15.5 kB, which is 19% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 69.6 kB or 86% of the original size.

Image Optimization

-18%

Potential reduce by 137.1 kB

  • Original 781.5 kB
  • After minification 644.4 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, Forclock needs image optimization as it can save up to 137.1 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

-71%

Potential reduce by 186.0 kB

  • Original 261.2 kB
  • After minification 238.3 kB
  • After compression 75.2 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 186.0 kB or 71% of the original size.

CSS Optimization

-77%

Potential reduce by 9.5 kB

  • Original 12.5 kB
  • After minification 10.3 kB
  • After compression 2.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. Forclock.ru needs all CSS files to be minified and compressed as it can save up to 9.5 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (28%)

Requests Now

53

After Optimization

38

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

forclock.ru

forclock.ru

1437 ms

www.forclock.ru

www.forclock.ru

311 ms

AC_RunActiveContent.js

AC_RunActiveContent.js

299 ms

protoaculous1.6.packed.js

protoaculous1.6.packed.js

430 ms

highslide-full.js

highslide-full.js

792 ms

style.css

style.css

313 ms

admin.css

admin.css

349 ms

graphics.css

graphics.css

308 ms

share.js

share.js

48 ms

none.gif

none.gif

248 ms

spacer.gif

spacer.gif

258 ms

logo.gif

logo.gif

263 ms

menu-sep.gif

menu-sep.gif

255 ms

long.png

long.png

355 ms

frank.png

frank.png

475 ms

rol11.jpg

rol11.jpg

585 ms

ferr.png

ferr.png

643 ms

bre1.png

bre1.png

569 ms

tag3.png

tag3.png

514 ms

n_37239.jpg

n_37239.jpg

599 ms

cupi.gif

cupi.gif

671 ms

str.gif

str.gif

703 ms

n_37880.jpg

n_37880.jpg

827 ms

n_37160.jpg

n_37160.jpg

828 ms

1345.jpg

1345.jpg

925 ms

n_36899.jpg

n_36899.jpg

852 ms

n_36192.jpg

n_36192.jpg

858 ms

n_8807.jpg

n_8807.jpg

901 ms

n_2265.jpg

n_2265.jpg

1109 ms

n_37931.jpg

n_37931.jpg

1113 ms

n_38023.jpg

n_38023.jpg

1114 ms

n_38022.jpg

n_38022.jpg

1145 ms

n_38021.jpg

n_38021.jpg

1184 ms

n_38020.jpg

n_38020.jpg

1198 ms

n_38019.jpg

n_38019.jpg

1328 ms

vk.jpg

vk.jpg

1311 ms

left_01.gif

left_01.gif

1318 ms

breguet.gif

breguet.gif

1337 ms

breitling.gif

breitling.gif

1364 ms

maurice.gif

maurice.gif

1391 ms

omega.gif

omega.gif

1492 ms

patek.gif

patek.gif

1461 ms

rado.gif

rado.gif

1508 ms

vacheron.gif

vacheron.gif

1535 ms

bottom-line.gif

bottom-line.gif

1511 ms

hit

hit

419 ms

b-share-icon.png

b-share-icon.png

176 ms

watch.js

watch.js

1 ms

cn_bg.jpg

cn_bg.jpg

1247 ms

toper.jpg

toper.jpg

1424 ms

menu-bg.gif

menu-bg.gif

1327 ms

btn_bg.gif

btn_bg.gif

1477 ms

content-bg.gif

content-bg.gif

1351 ms

bascet.gif

bascet.gif

1254 ms

str2.gif

str2.gif

1222 ms

hit

hit

137 ms

drop-shadow.png

drop-shadow.png

108 ms

zoomout.cur

zoomout.cur

187 ms

loader.white.gif

loader.white.gif

192 ms

SEO Factors

forclock.ru SEO score

0

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    N/A

  • Encoding

    WINDOWS-1251

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

forclock.ru

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