4.7 sec in total
881 ms
3.7 sec
173 ms
Visit otspb.ru now to see the best up-to-date Otspb content for Russia and also check out these interesting facts you probably never knew about otspb.ru
Маршруты общественного транспорта СПб. Расписание автобусов Санкт-Петербурга. Городской транспорт Санкт-Петербурга.
Visit otspb.ruWe analyzed Otspb.ru page load time and found that the first response time was 881 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
otspb.ru performance score
name
value
score
weighting
Value2.8 s
55/100
10%
Value2.8 s
82/100
25%
Value2.9 s
95/100
10%
Value980 ms
28/100
30%
Value0
100/100
15%
Value8.8 s
36/100
10%
881 ms
433 ms
308 ms
296 ms
19 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 9% of them (5 requests) were addressed to the original Otspb.ru, 12% (7 requests) were made to Api-maps.yandex.ru and 12% (7 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (894 ms) relates to the external source Api-maps.yandex.ru.
Page size can be reduced by 209.5 kB (43%)
484.6 kB
275.1 kB
In fact, the total size of Otspb.ru main page is 484.6 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. 40% of websites need less resources to load. HTML takes 235.6 kB which makes up the majority of the site volume.
Potential reduce by 155.1 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 155.1 kB or 66% of the original size.
Potential reduce by 518 B
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. Otspb images are well optimized though.
Potential reduce by 49.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 49.2 kB or 33% of the original size.
Potential reduce by 4.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. Otspb.ru needs all CSS files to be minified and compressed as it can save up to 4.7 kB or 77% of the original size.
Number of requests can be reduced by 31 (63%)
49
18
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Otspb. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and as a result speed up the page load time.
otspb.ru
881 ms
main.css
433 ms
main.js
308 ms
296 ms
adsbygoogle.js
19 ms
7988.js
429 ms
share.js
23 ms
count.js
285 ms
640 ms
combine.xml
894 ms
out-str.png
184 ms
ca-pub-1057613423383195.js
101 ms
zrt_lookup.html
91 ms
show_ads_impl.js
104 ms
hit
313 ms
aci.js
217 ms
top100.jcn
467 ms
logo
311 ms
ads
214 ms
osd.js
23 ms
ads
324 ms
109 ms
286 ms
hit
195 ms
13679439019692687543
204 ms
abg.js
216 ms
m_js_controller.js
319 ms
googlelogo_color_112x36dp.png
186 ms
top100.scn
226 ms
569 ms
plusone.js
262 ms
close.png
221 ms
202511.js
566 ms
ya-share-cnt.html
33 ms
watch.js
3 ms
b-share-icon.png
55 ms
b-share_counter_large.png
140 ms
793 ms
share_count
863 ms
dk
860 ms
fql.query
510 ms
share.php
696 ms
x_button_blue2.png
148 ms
s
86 ms
imgad
35 ms
mobile_unified_button_icon_white.png
34 ms
Rf2QnA3orEL6Eez56HJgxRuQ77qJyxbefnbSCBE0iUQ.js
31 ms
cb=gapi.loaded_0
82 ms
ef50ac9e93aaebe3299791c79f277f8e.cur
131 ms
match
296 ms
3ce22e999d54bb9ca8150a59207f9d3e.cur
163 ms
4965b66fe115b2f2ed500ece66514d86.cur
324 ms
77492cf358d8b12629399322926c93f2.cur
438 ms
showad_full.js
377 ms
1x1.gif
266 ms
adi
435 ms
activeview
19 ms
activeview
26 ms
otspb.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
otspb.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
otspb.ru SEO score
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
RU
RU
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Otspb.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 Otspb.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.
otspb.ru
Open Graph description is not detected on the main page of Otspb. 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: