Suggestions Summary
Enable compression
Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.
Enable compression for the following resources to reduce their transfer size by 556.6KiB (75% reduction).
Compressing http://size.name/media/mj/9ccdbe.js could save 281KiB (68% reduction).
Compressing http://size.name/media/mj/b573e5.css could save 223.3KiB (87% reduction).
Compressing http://size.name/media/widgetkit/widgets/mediaplayer/mediaelement/mediaelement-and-player.js?_=1521555013336 could save 40.5KiB (72% reduction).
Compressing http://size.name/media/widgetkit/widgets/lightbox/js/lightbox.js?_=1521555013335 could save 10.4KiB (64% reduction).
Compressing http://size.name/media/widgetkit/widgets/spotlight/js/spotlight.js?_=1521555013337 could save 1.4KiB (57% reduction).
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.
None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.Remove render-blocking JavaScript:
http://size.name/media/mj/9ccdbe.jsOptimize CSS Delivery of the following:
http://size.name/media/mj/b573e5.css
Prioritize visible content
Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.
The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.
Only about 5% of the final above-the-fold content could be rendered with the full HTML response .
Leverage browser caching
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:
http://size.name/data/images/pic.png
(expiration not specified)
http://size.name/data/images/sorting_sprite.png (expiration not specified)http://size.name/media/mj/9ccdbe.js (expiration not specified)http://size.name/media/mj/b573e5.css (expiration not specified)http://size.name/templates/mobile_basic/vendor/jqm/images/ajax-loader.gif (expiration not specified)http://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js (60 minutes)https://mc.yandex.ru/metrika/watch.js (60 minutes)http://www.google-***ytics.com/ga.js (2 hours)
Size tap targets appropriately
Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.
The following tap targets are close to other nearby tap targets and may need additional spacing around them.
The tap target <th class="footable-sortable">Номер</th> is close to 1 other tap targets .
The tap target <a href="imagebig/***679…cc7590ee50.jpg" class="ui-link"></a> and 3 others are close to other tap targets .
The tap target <div id="abgc" class="abgc">Реклама отGoogle</div>
is close to 1 other tap targets .
Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 15.5KiB (66% reduction).
Compressing and resizing http://size.name/imagesmall/55220ef34820188ef6217c651ebd9eaa.jpg could save 10KiB (94% reduction).
Compressing http://size.name/imagesmall/4f8818e16c0951f498565156f077a611.jpg could save 3.7KiB (49% reduction).
Compressing http://size.name/imagesmall/8480a38e3a175c0358b15ca91449f60f.jpg could save 1.3KiB (45% reduction).
Compressing http://counter.rambler.ru/top100.cnt?2780261 could save 407B (22% reduction).
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
Configure the viewport
Your page specifies a viewport matching the device’s size, which allows it to render properly on all devices. Learn more about configuring viewports.
Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Minify CSS
Your CSS is minified. Learn more about minifying CSS.
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
hypestat.com
Заголовок ответа сервера
| HTTP/1.1 200 OK |
| Server: nginx/1.2.1 |
| Date: Mon, 24 Apr 2017 07:13:04 GMT |
| Content-Type: text/html; charset=utf-8 |
| Transfer-Encoding: chunked |
| Connection: close |
| X-Powered-By: PHP/5.4.45-0+deb7u7 |
whois.uanic.name
