25.3 sec in total
573 ms
24.3 sec
365 ms
Visit spb.rusavtobus.ru now to see the best up-to-date Spb Rusavtobus content for Russia and also check out these interesting facts you probably never knew about spb.rusavtobus.ru
Поисковый сервис по маршрутам Санкт-Петербурга: маршрутные такси, автобусы, троллейбусы, трамваи, метро. Самая полная карта общественного транспорта Санкт-Петербурга. Проезд от любого дома до любого д...
Visit spb.rusavtobus.ruWe analyzed Spb.rusavtobus.ru page load time and found that the first response time was 573 ms and then it took 24.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
spb.rusavtobus.ru performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value13.4 s
0/100
25%
Value10.8 s
6/100
10%
Value2,250 ms
6/100
30%
Value0.045
99/100
15%
Value21.7 s
1/100
10%
573 ms
516 ms
518 ms
515 ms
532 ms
Our browser made a total of 112 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Spb.rusavtobus.ru, 51% (57 requests) were made to Resource.rusavtobus.ru and 14% (16 requests) were made to Maps.google.com. The less responsive or slowest element that took the longest time to load (20.1 sec) relates to the external source Vk.com.
Page size can be reduced by 1.2 MB (65%)
1.9 MB
654.7 kB
In fact, the total size of Spb.rusavtobus.ru main page is 1.9 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. 70% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 148.2 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 148.2 kB or 85% of the original size.
Potential reduce by 8.7 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. Spb Rusavtobus images are well optimized though.
Potential reduce by 934.4 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 934.4 kB or 71% of the original size.
Potential reduce by 138.0 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. Spb.rusavtobus.ru needs all CSS files to be minified and compressed as it can save up to 138.0 kB or 84% of the original size.
Number of requests can be reduced by 70 (68%)
103
33
The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Spb Rusavtobus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 47 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
spb.rusavtobus.ru
573 ms
style_widget_walk_main.css
516 ms
new_ui_10.css
518 ms
screen_incity_all.css
515 ms
jquery.ui.selectmenu.css
532 ms
jquery-ui-1.8.14.custom.css
525 ms
mapchooser.js
527 ms
jquery-1.6.1.min.js
815 ms
key_spb.js
602 ms
jquery.xdomainajax_ru.js
603 ms
mapslib.js
610 ms
route_new.js
607 ms
const_spb.js
622 ms
const_ru_10.js
828 ms
searchInterface.js
799 ms
search.js
709 ms
jquery-ui-1.8.14.custom.min.js
808 ms
jquery.ui.selectmenu.js
720 ms
jquery.select_skin.js
807 ms
jquery.autocomplete.js
847 ms
md5.js
910 ms
login_presentation.js
917 ms
login_controller.js
914 ms
new_ui_10.js
918 ms
radiostyle.js
912 ms
transports.js
962 ms
objects.js
1042 ms
myroutes.js
1044 ms
city.js
1044 ms
js
96 ms
share42.js
1070 ms
adsbygoogle.js
59 ms
dojo.js
1167 ms
index.xml
304 ms
print.css
132 ms
index.xml
670 ms
_YMaps.css
125 ms
_YMaps.js
642 ms
logo_new.gif
99 ms
flag_en.gif
134 ms
rus.gif
133 ms
bel.gif
134 ms
kzt.gif
134 ms
en.gif
132 ms
aus.gif
333 ms
ukr.gif
333 ms
arrow.gif
333 ms
renew-k.gif
330 ms
revers-k.gif
330 ms
find_new.gif
328 ms
previous-k.gif
432 ms
new-search-k.gif
434 ms
select_new.gif
431 ms
lenta-7.gif
432 ms
hint_img0.gif
432 ms
hint_img3.gif
430 ms
hint_img1.gif
575 ms
hint_img2.gif
576 ms
feedback_renew.gif
574 ms
feedback_new.gif
577 ms
bg.jpg
662 ms
expand_map_3.gif
545 ms
ca-pub-4533964735969701.js
266 ms
zrt_lookup.html
265 ms
show_ads_impl.js
162 ms
context.js
414 ms
loading.gif
578 ms
watch.js
102 ms
common.js
156 ms
map.js
179 ms
util.js
238 ms
geocoder.js
176 ms
icons.png
433 ms
ads
280 ms
StaticMapService.GetMapImage
60 ms
osd.js
40 ms
onion.js
36 ms
openhand_8_8.cur
153 ms
ViewportInfoService.GetViewportInfo
128 ms
stats.js
46 ms
controls.js
41 ms
context_static_r1084.js
435 ms
css
104 ms
transparent.png
72 ms
marker.js
56 ms
google4.png
73 ms
mapcnt6.png
73 ms
sv5.png
74 ms
tmapctrl.png
42 ms
cb_scout5.png
56 ms
tmapctrl4.png
38 ms
imgs8.png
41 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
65 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
85 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
134 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
195 ms
vt
43 ms
vt
41 ms
vt
39 ms
vt
40 ms
vt
79 ms
vt
122 ms
vt
73 ms
AuthenticationService.Authenticate
186 ms
openapi.js
20100 ms
149851
166 ms
watch.js
1 ms
y90
196 ms
www.360totalsecurity.com
287 ms
www.tripadvisor.ru
430 ms
2-jNKlxgmTq40000gQ0000AElBXyS0M5cvKadh800004kl4tprxQT_8V196qy4Hl3PDKfB00000bhlkq03vJje6G0R2mAnUL1RlwEEimeT8HtmN1__________yFs_fuHAIeqX7V1NiB=jdZn8PK2cm5kGxS2YQhi0mAOfBkzlegtLLIF1RspNvGl1QMkQaC8YBcx7Fa6lAM3mmAcW0cTgaSM4u-xnF3w0P-j6-ZUcGoWcI0QivUa1g-T0HYqc1e6sP3F7DgGKmUKbN07fujCgACr42z1iG6oe5800hcgHnOJnOyFpR5LL8y5ph5jSqm7ql__________3zF__________m_20DzKUnC0=GDvh89K2cm5kGxS2Cec34vZ__________m-AjKMVamAziX2tpmAbh80y1OYksPPnlA22X0Ic1fsgDnCJZxffeaGAdxpl28S4cHwWaDONhv284zcGQXYdZ4gei41PSmT1iG6oe5000hcgDnCJnOyFql__________3zF__________m_20DzKUn00=064sMfK2cm5kGxS2CucHcwcO__________yFYh5Ixb45lRG083W1fQm-3mE8kzDlCGIyht4E0wOndQMdUXMFkG6aF06Vje44T0kP1g2J73gpcieLhvCSEhIQoXNPc1f1sf1g69IKi1IdZXcei41PSmT1iG6oeD000hcbfteLnOyFql__________3zF__________m_20DzKVH80
140 ms
QuotaService.RecordEvent
27 ms
spb.rusavtobus.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
[id] attributes on active, focusable elements are not unique
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
spb.rusavtobus.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
Page has valid source maps
spb.rusavtobus.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Spb.rusavtobus.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 Spb.rusavtobus.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.
spb.rusavtobus.ru
Open Graph description is not detected on the main page of Spb Rusavtobus. 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: