4 sec in total
840 ms
3 sec
116 ms
Click here to check amazing 999 content. Otherwise, check out these important facts you probably never knew about 999.by
999 - комфортная жизнь онлайн
Visit 999.byWe analyzed 999.by page load time and found that the first response time was 840 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
999.by performance score
name
value
score
weighting
Value0.7 s
100/100
10%
Value0.7 s
100/100
25%
Value1.0 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.7 s
100/100
10%
840 ms
247 ms
379 ms
251 ms
253 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 94% of them (67 requests) were addressed to the original 999.by, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain 999.by.
Page size can be reduced by 112.4 kB (45%)
252.4 kB
140.0 kB
In fact, the total size of 999.by main page is 252.4 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. 65% of websites need less resources to load. Images take 122.2 kB which makes up the majority of the site volume.
Potential reduce by 63.0 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 63.0 kB or 81% of the original size.
Potential reduce by 17.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, 999 needs image optimization as it can save up to 17.4 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 32.0 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 32.0 kB or 60% of the original size.
Number of requests can be reduced by 50 (81%)
62
12
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 999. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
999.by
840 ms
normalize.css
247 ms
foundation.min.css
379 ms
foundation-icons.css
251 ms
imgareaselect-default.css
253 ms
cropper.min.css
253 ms
mediaelementplayer.min.css
256 ms
DateTimePicker.css
370 ms
jquery-ui-timepicker-addon.css
375 ms
font.css
375 ms
system.css
386 ms
foundation_ext.css
387 ms
image.viewer.css
493 ms
icons.css
503 ms
mime-sprite.css
501 ms
toggle-switch.css
500 ms
redactor.css
505 ms
inverse_main.css
510 ms
style.css
616 ms
styles.css
623 ms
chosen.css
625 ms
jquery.min.js
756 ms
foundation.min.js
767 ms
jquery.yiiactiveform.js
636 ms
jquery.imgareaselect.pack.js
740 ms
cropper.min.js
748 ms
mediaelement-and-player.min.js
878 ms
jquery-ui.min.js
1028 ms
DateTimePicker.js
867 ms
jquery-ui-i18n.min.js
875 ms
jquery-ui-timepicker-addon.js
883 ms
system.js
887 ms
WSClient.js
991 ms
punycode.min.js
999 ms
jquery-ui.js
1405 ms
php.js
1009 ms
js
79 ms
image.viewer.js
902 ms
jquery.browser.min.js
879 ms
jquery-ex.js
880 ms
jquery.path.js
892 ms
ajaxupload.js
897 ms
dmuploader.min.js
906 ms
modernizr.js
881 ms
jquery.cookie.js
880 ms
soundmanager2.js
1032 ms
jquery.ba-bbq.min.js
890 ms
jquery.history.js
902 ms
redactor.min.js
1114 ms
ru.js
885 ms
chosen.jquery.js
901 ms
jquery.yiilistview.js
938 ms
vk-logo.png
125 ms
facebook-logo.png
128 ms
logo.png
126 ms
login.png
125 ms
analytics.js
22 ms
lmi.png
132 ms
left-icons.png
132 ms
h-icons.png
472 ms
icons-small.png
227 ms
opensans-regular-webfont.woff
228 ms
opensans-semibold-webfont.woff
233 ms
opensans-light-webfont.woff
243 ms
open_sans_condensed_bold-webfont.woff
366 ms
open_sans_condensed__light-webfont.woff
473 ms
opensans-bold-webfont.woff
353 ms
opensans-extrabold-webfont.woff
358 ms
collect
24 ms
to-top.png
299 ms
collect
51 ms
999.by accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
999.by best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
999.by SEO score
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 999.by can be misinterpreted by Google and other search engines. Our service has detected that English 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 999.by 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.
999.by
Open Graph description is not detected on the main page of 999. 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: