12.5 sec in total
636 ms
10.2 sec
1.6 sec
Visit peterburg.ru now to see the best up-to-date Peterburg content for Russia and also check out these interesting facts you probably never knew about peterburg.ru
Петербург.ру – первый туристический гид с актуальной, ежедневно обновляемой информацией о местах и событиях города.
Visit peterburg.ruWe analyzed Peterburg.ru page load time and found that the first response time was 636 ms and then it took 11.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
peterburg.ru performance score
name
value
score
weighting
Value5.8 s
4/100
10%
Value8.2 s
2/100
25%
Value11.1 s
6/100
10%
Value2,150 ms
6/100
30%
Value0.031
100/100
15%
Value18.8 s
3/100
10%
636 ms
864 ms
82 ms
321 ms
304 ms
Our browser made a total of 112 requests to load all elements on the main page. We found that 46% of them (51 requests) were addressed to the original Peterburg.ru, 11% (12 requests) were made to Vk.com and 4% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (7.2 sec) belongs to the original domain Peterburg.ru.
Page size can be reduced by 607.1 kB (23%)
2.6 MB
2.0 MB
In fact, the total size of Peterburg.ru main page is 2.6 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. 65% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 43.9 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 43.9 kB or 74% of the original size.
Potential reduce by 159.9 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. Peterburg images are well optimized though.
Potential reduce by 243.1 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 243.1 kB or 70% of the original size.
Potential reduce by 160.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. Peterburg.ru needs all CSS files to be minified and compressed as it can save up to 160.3 kB or 80% of the original size.
Number of requests can be reduced by 44 (43%)
103
59
The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Peterburg. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
peterburg.ru
636 ms
www.peterburg.ru
864 ms
css
82 ms
css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css
321 ms
css__LeQxW73LSYscb1O__H6f-j_jdAzhZBaesGL19KEB6U.css
304 ms
css_zWfPetBrjxwjs6Iur4IGyOU5Li5P2UPXpPjft7fFsiw.css
301 ms
css_rR4N_QWgpIZpZIsj2H9dSzyAv7LBj2NvR6P1MuWc6qw.css
437 ms
css_u8OU8yD1VcEdLnpZ4EQ-GfLaLyDsiP2pcMS_W6KuArQ.css
736 ms
css_xyxflaeW5Ejqc5LYl3W_rwe1l9QvYsCm8MX0ekb2HMM.css
425 ms
modernizr.min.js
575 ms
jquery.min.js
130 ms
js_3TykeRWpejhD4-J3vdlaNXdULg9xhOZhbsppK0o2bUs.js
568 ms
jquery-ui.min.js
201 ms
js_yAicZujtqUhpCyuBiQyVA1uGwMX8V0A0ym_4Jb35kBQ.js
724 ms
js_4WsmM3Xms5onUz4Q30yuy5N1g7-NHLHUW8tP7PSCzio.js
1379 ms
js_uePHuAl4UYOs0aGzBFi5LRTHY6uVrfl2HTqqDE2TYXc.js
560 ms
openapi.js
418 ms
sjs.php
218 ms
js_vDekGgcY3yRp9wnHkyr8NucGgIE0FZLEBnPBztF62bg.js
426 ms
plusone.js
1163 ms
all.js
1137 ms
ga.js
494 ms
bg.jpg
1036 ms
logo-vector.svg
1366 ms
main-sprites.png
1004 ms
nedelya.jpg
1588 ms
peticiya1.jpg
3940 ms
sad1.jpg
5048 ms
poezd1.jpg
1900 ms
fontan1.jpg
4600 ms
main-slider-right.png
4657 ms
bg_back.png
1773 ms
sunlights-in-cafeteria_0.jpg
2503 ms
top-str-12_5.jpg
2503 ms
1_593_0.jpg
3284 ms
corner.png
2822 ms
top-str-12_2.jpg
3580 ms
visits-main.png
3578 ms
tur_po_baram19.jpg
4411 ms
frida2_1.jpg
4577 ms
ivan2_1.jpg
4720 ms
hab1.jpg
5288 ms
8_26.jpg
4983 ms
leningradcenter.com-1551_--_kopiya_0.jpg
5450 ms
1_587.jpg
5518 ms
c-lzggyrp3i_1.jpg
5440 ms
3_1_1.jpg
5406 ms
fecrhqyf3qm_1_0.jpg
5756 ms
vystavka_obuvi2_1.jpg
5588 ms
shou_varekai_ot_cirque_du_soleil2_1.jpg
6003 ms
elton_dzhon1_0_0.jpg
5885 ms
upload-movie_posters-9-2-2-8171229-95b68e1d7ade3c681839e94f22b61221.jpg
6954 ms
upload-movie_posters-7-2-1-8178127-aeb1a3af682156703239286461e9a6cf.jpg
6628 ms
upload-movie_posters-6-4-1-8170146-44b6272abe836d9932807f0c753ca771.jpg
6294 ms
upload-movie_posters-1-7-7-8158771-37b294243a9855e2093dbd4645272974.jpg
7171 ms
festival-leonardo.jpg
6802 ms
uqFpzDRr-oQw71LHgsWhDw.ttf
765 ms
53FiIA9tShIIWgCiX49s-vesZW2xOQ-xsNqO47m55DA.ttf
795 ms
GXkxFoTpyMRlYXE2XJ40uw.ttf
796 ms
3875EdM-9ys3OtdHL2b2gy3USBnSvpkopQaUR-2r7iU.ttf
795 ms
upload.gif
1497 ms
ajs.php
1029 ms
widget_community.php
1608 ms
__utm.gif
266 ms
cb=gapi.loaded_0
74 ms
show_ads.js
73 ms
lg.php
122 ms
306 ms
ca-pub-8917483415235212.js
406 ms
zrt_lookup.html
403 ms
show_ads_impl.js
228 ms
xd_arbiter.php
520 ms
xd_arbiter.php
751 ms
aci.js
410 ms
hit
430 ms
watch.js
164 ms
gradient-left.png
4613 ms
slider-arrows2.png
4753 ms
widget_community.php
335 ms
ads
314 ms
osd.js
166 ms
168 ms
281 ms
loader_nav19239_3.js
206 ms
lite.css
214 ms
lite.js
513 ms
lang3_0.js
297 ms
widget_community.css
301 ms
xdm.js
299 ms
al_community.js
333 ms
13451327258148321268
185 ms
abg.js
209 ms
m_js_controller.js
239 ms
googlelogo_color_112x36dp.png
130 ms
407 ms
s
103 ms
x_button_blue2.png
177 ms
2dO95PWEzvw.jpg
476 ms
A4R7U4opkOY.jpg
1268 ms
SerjnI-7wk8.jpg
505 ms
u8R87SfiNXI.jpg
503 ms
e_48cad445.jpg
502 ms
i5ZlDiBctKQ.jpg
503 ms
YA-tmpJkPHc.jpg
378 ms
camera_50.png
693 ms
ZWHbO4AP2jQ.jpg
834 ms
9WABKACk2oY.jpg
456 ms
vihGdqNQxIw.jpg
1705 ms
Rf2QnA3orEL6Eez56HJgxRuQ77qJyxbefnbSCBE0iUQ.js
45 ms
w_logo.png
177 ms
match
286 ms
css_ufKjcAkUGM_iHRkwWlYKNf8zGjyM_kYJPdbcLtZl2t0.css
140 ms
peterburg.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
Links do not have a discernible name
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
peterburg.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
peterburg.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
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Peterburg.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 Peterburg.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.
peterburg.ru
Open Graph description is not detected on the main page of Peterburg. 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: