3 sec in total
547 ms
2.3 sec
169 ms
Welcome to 58bus.ru homepage info - get ready to check 58 Bus best content for Russia right away, or after learning these important things about 58bus.ru
Общественный транспорт города Пенза онлайн.
Visit 58bus.ruWe analyzed 58bus.ru page load time and found that the first response time was 547 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
58bus.ru performance score
name
value
score
weighting
Value1.3 s
98/100
10%
Value1.3 s
100/100
25%
Value2.5 s
98/100
10%
Value10 ms
100/100
30%
Value0
100/100
15%
Value1.4 s
100/100
10%
547 ms
6 ms
12 ms
138 ms
406 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 44% of them (29 requests) were addressed to the original 58bus.ru, 48% (32 requests) were made to B.tile.openstreetmap.org and 3% (2 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source B.tile.openstreetmap.org.
Page size can be reduced by 328.2 kB (30%)
1.1 MB
758.6 kB
In fact, the total size of 58bus.ru main page is 1.1 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. 45% of websites need less resources to load. Images take 663.0 kB which makes up the majority of the site volume.
Potential reduce by 34.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 34.2 kB or 88% of the original size.
Potential reduce by 19.3 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. 58 Bus images are well optimized though.
Potential reduce by 230.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 230.4 kB or 69% of the original size.
Potential reduce by 44.3 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. 58bus.ru needs all CSS files to be minified and compressed as it can save up to 44.3 kB or 85% of the original size.
Number of requests can be reduced by 17 (26%)
65
48
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 58 Bus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
58bus.ru
547 ms
leaflet.css
6 ms
leaflet.js
12 ms
styles.css
138 ms
jquery-1.11.1.min.js
406 ms
messi.min.css
273 ms
messi.min.js
274 ms
jscode.js
417 ms
config.js
275 ms
styles.css
276 ms
analytics.js
31 ms
badge_appstore-lrg.png
150 ms
getRoutes.php
344 ms
10644.png
552 ms
10644.png
551 ms
10645.png
550 ms
10645.png
550 ms
10643.png
551 ms
10643.png
549 ms
10644.png
631 ms
10644.png
634 ms
10645.png
637 ms
10645.png
714 ms
10646.png
714 ms
10646.png
637 ms
10643.png
714 ms
10643.png
715 ms
10646.png
800 ms
10646.png
716 ms
10644.png
798 ms
10644.png
798 ms
10645.png
797 ms
10645.png
800 ms
10643.png
800 ms
10643.png
882 ms
10646.png
883 ms
10646.png
882 ms
10644.png
883 ms
10644.png
881 ms
10645.png
883 ms
10645.png
1013 ms
10643.png
1016 ms
10643.png
1015 ms
10646.png
1013 ms
10646.png
1014 ms
top_panel_x.png
135 ms
routes_button_up.png
138 ms
top_splitter.png
136 ms
station_search_button_up.png
138 ms
fav_button_up.png
139 ms
traffic_off.png
268 ms
1.gif
667 ms
2.gif
546 ms
bottom_panel_x.png
275 ms
android_small_up.png
276 ms
check_no.png
402 ms
collect
12 ms
getZones.php
617 ms
routes_button_down.png
138 ms
close16.png
135 ms
check_yes.png
139 ms
block_header_x.png
138 ms
block_bus_ico.png
269 ms
check_gray.png
273 ms
block_troll_ico.png
274 ms
block_marsh_ico.png
275 ms
58bus.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.
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
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
Image elements do not have [alt] attributes
58bus.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
58bus.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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 58bus.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 58bus.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.
58bus.ru
Open Graph description is not detected on the main page of 58 Bus. 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: