6.3 sec in total
1.1 sec
5.1 sec
140 ms
Click here to check amazing SERIES60 content for Russia. Otherwise, check out these important facts you probably never knew about series60.ru
Новости, программы и игры для iphone, symbian, android.
Visit series60.ruWe analyzed Series60.ru page load time and found that the first response time was 1.1 sec and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
series60.ru performance score
name
value
score
weighting
Value3.6 s
31/100
10%
Value4.2 s
45/100
25%
Value10.2 s
8/100
10%
Value4,660 ms
0/100
30%
Value0.166
71/100
15%
Value27.9 s
0/100
10%
1097 ms
235 ms
259 ms
233 ms
260 ms
Our browser made a total of 121 requests to load all elements on the main page. We found that 42% of them (51 requests) were addressed to the original Series60.ru, 34% (41 requests) were made to St6-21.vk.com and 6% (7 requests) were made to Vk.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source St6-21.vk.com.
Page size can be reduced by 473.4 kB (16%)
3.0 MB
2.5 MB
In fact, the total size of Series60.ru main page is 3.0 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. 60% of websites need less resources to load. Javascripts take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 59.5 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 59.5 kB or 79% of the original size.
Potential reduce by 13.1 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. SERIES60 images are well optimized though.
Potential reduce by 324.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 324.2 kB or 15% of the original size.
Potential reduce by 76.7 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. Series60.ru needs all CSS files to be minified and compressed as it can save up to 76.7 kB or 14% of the original size.
Number of requests can be reduced by 82 (72%)
114
32
The browser has sent 114 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SERIES60. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 49 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
series60.ru
1097 ms
style.css
235 ms
wordpress-file-monitor.php
259 ms
style.min.css
233 ms
srr-css.css
260 ms
twitter-feed.css
259 ms
jquery.js
425 ms
jquery-migrate.min.js
349 ms
flowplayer-3.2.6.min.js
363 ms
contentslider.js
349 ms
slides.min.jquery.js
359 ms
superfish-1.4.8.js
370 ms
jCarouselLite.js
464 ms
srr-js.js
465 ms
fancy_white.css
481 ms
cforms.js
491 ms
default.css
495 ms
openapi.js
381 ms
openapi.js
393 ms
form.js
715 ms
widget-2.0.js
546 ms
core.min.js
439 ms
datepicker.min.js
487 ms
wp-embed.min.js
471 ms
wp-emoji-release.min.js
347 ms
calendar.css
131 ms
openapi.a2ed73393cad04481c1dfb3f7794921f.js
252 ms
openapi.a2ed73393cad04481c1dfb3f7794921f.js
266 ms
logo.jpg
123 ms
rss.png
136 ms
lj.png
134 ms
vkontakte.png
135 ms
twitter.png
120 ms
facebook.png
120 ms
b4da605ee_100x90.png
244 ms
5b648aa09_100x90.png
243 ms
932ab94c4_100x90.png
243 ms
5e4bb694f_100x90.png
248 ms
b32e6b851_405x250.png
291 ms
2b0122935_120x90.png
251 ms
b7091263c_300x225.png
359 ms
b4d443cfd_60x50.png
348 ms
e074de710_60x50.png
348 ms
186ab492a_60x50.png
368 ms
6542f5cf3_300x225.png
505 ms
256aa88b3_60x50.png
414 ms
eba1b0e14_60x50.png
474 ms
2b0122935_300x225.png
483 ms
7634c811a_60x50.png
474 ms
906fa5970_60x50.png
487 ms
d67080f19_300x225.png
549 ms
12d65236b_60x50.png
594 ms
aa4c6d23a_60x50.png
594 ms
upload.gif
133 ms
bgr_tabs_title.gif
558 ms
bgr_tabs_title_a.gif
565 ms
list_a.gif
586 ms
widget_community.php
191 ms
jquery.min.js
272 ms
hit
244 ms
widgets.js
44 ms
watch.js
4 ms
ga.js
28 ms
arrow-superfish-down.png
572 ms
__utm.gif
19 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
141 ms
loader_nav210011395769_3.js
293 ms
fonts_cnt.c7a76efe.css
1011 ms
lite.ca486089.css
686 ms
lang3_2.js
408 ms
polyfills.f358dd9d.js
634 ms
vkui.43318ab6.css
717 ms
xdm.js
544 ms
ui_common.5f35f406.css
631 ms
react.759f82b6.js
817 ms
vkui.847cc706.js
1005 ms
vkcom-kit.7eaafce2.css
844 ms
vkcom-kit.96cc8a1b.js
1087 ms
vkcom-kit-icons.7c2762f5.js
912 ms
state-management.148fcc7d.js
930 ms
audioplayer-lib.93b52d88.css
932 ms
audioplayer-lib.e56dce24.js
1107 ms
common.26db631c.js
1774 ms
ui_common.b1037836.css
1085 ms
ui_common.b196c3c7.js
1102 ms
audioplayer.7787a5d3.css
1093 ms
audioplayer.45a2fe51.js
1102 ms
widget_community.4978d481.css
1135 ms
5441c5ed.c6a2c19e.js
1187 ms
aa3c5e05.0d43f81d.js
1193 ms
likes.33883160.css
1189 ms
likes.349be5f5.js
1201 ms
react.ec1d5408.js
1249 ms
vkcom-kit.4d5aaa48.css
1282 ms
vkcom-kit.c1617729.js
1296 ms
vkui.96324928.js
1449 ms
vkcom-kit-icons.4dba2d7c.js
1296 ms
audioplayer-lib.85b39ca5.css
1336 ms
audioplayer-lib.750e095c.js
1455 ms
state-management.d691d00d.js
1390 ms
c3d11fba.a7640b83.js
1387 ms
0fc69f32.5fd0209f.js
1437 ms
e7eaa3a9.8f5524ee.js
1480 ms
57703e15.a2698231.js
1492 ms
settings
93 ms
hit
530 ms
_form.js
93 ms
lite.bcf10ece3464fec8b554bde483fa2494.js
426 ms
yandex-hint.png
92 ms
community.be2fc20a.css
988 ms
base.4d099727.css
917 ms
edb6ffde.1c9c7d5b.js
1417 ms
community.a432030a.js
879 ms
c_97b20b62.jpg
623 ms
QulWsGFAn5k.png
633 ms
_E9vzD1VztMnM1cgRzfQadR59nhsCEuZ2C7i_LvqJ0QnEDg8ul_c1OylCihQMeZSLHWFdvt5HuCzMoppY52KJmAv.jpg
358 ms
09kBVNe_csLsNPuQJAGAafg1pj-dh23w8_lxz7ETowaCxwxOK2m6xnV9CbDjjy4DbWWlflT96emhpXMUTEh-ajEI.jpg
498 ms
tc3_WQxCEx4.jpg
599 ms
7x48Uozag4EJQcVa67pwjaF_JK64CYJdkVTxrXr0R9mu92vMh5l3PIvdfdrQNssuePPueg.jpg
502 ms
IhKv6IEdbW6Bzg-EUEpP3szfjd2JNNToveI5SM8rpHBCpkUIuMd2ku6PGMR1Lwh-BZRZuuI_.jpg
503 ms
upload.gif
89 ms
series60.ru accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
series60.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
series60.ru SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
RU
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Series60.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that Series60.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.
series60.ru
Open Graph description is not detected on the main page of SERIES60. 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: