5.9 sec in total
408 ms
4.8 sec
720 ms
Click here to check amazing Peterburg content for Russia. Otherwise, check out these important facts you probably never knew about peterburg.biz
Ваш путеводитель по достопримечательностям Санкт-Петербурга - туристическое агентство «Мой Петербург» - www.Peterburg.biz
Visit peterburg.bizWe analyzed Peterburg.biz page load time and found that the first response time was 408 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
peterburg.biz performance score
name
value
score
weighting
Value5.0 s
9/100
10%
Value5.1 s
24/100
25%
Value7.3 s
29/100
10%
Value7,480 ms
0/100
30%
Value0.009
100/100
15%
Value16.1 s
6/100
10%
408 ms
1010 ms
377 ms
633 ms
647 ms
Our browser made a total of 139 requests to load all elements on the main page. We found that 47% of them (66 requests) were addressed to the original Peterburg.biz, 10% (14 requests) were made to Vk.com and 5% (7 requests) were made to Mc.yandex.ru. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Peterburg.biz.
Page size can be reduced by 868.2 kB (42%)
2.1 MB
1.2 MB
In fact, the total size of Peterburg.biz main page is 2.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. 60% of websites need less resources to load. Images take 965.2 kB which makes up the majority of the site volume.
Potential reduce by 229.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 229.5 kB or 84% of the original size.
Potential reduce by 41.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 528.5 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 528.5 kB or 69% of the original size.
Potential reduce by 68.2 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.biz needs all CSS files to be minified and compressed as it can save up to 68.2 kB or 82% of the original size.
Number of requests can be reduced by 55 (41%)
135
80
The browser has sent 135 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 32 to 1 for JavaScripts and as a result speed up the page load time.
peterburg.biz
408 ms
www.peterburg.biz
1010 ms
template_css.css
377 ms
jquery-1.3.js
633 ms
jquery-1.4.2.min.js
647 ms
jquery.lightbox-0.5.min.js
263 ms
openapi.js
519 ms
jquery-1.4.4.min.js
662 ms
adsbygoogle.js
10 ms
share.js
13 ms
fcode.js
324 ms
ti.js
5 ms
head.jpg
1011 ms
lnav.png
144 ms
navrazd.png
143 ms
rnav.png
141 ms
menu1.png
534 ms
muzey.jpg
146 ms
teatr.jpg
250 ms
ploshad.jpg
254 ms
hram.jpg
256 ms
most.jpg
267 ms
pam.jpg
375 ms
sad.jpg
380 ms
doma.jpg
385 ms
street.jpg
444 ms
nab.jpg
530 ms
unbanal.gif
1012 ms
menu2.jpg
531 ms
pero.jpg
577 ms
duel.jpg
624 ms
myth.jpg
641 ms
mist.jpg
651 ms
mp.jpg
708 ms
stihii.jpg
749 ms
bal.jpg
770 ms
menu3.jpg
814 ms
101hotels.png
843 ms
4rek-cds16.jpg
998 ms
4rekzoom.jpg
898 ms
4rekgrand.jpg
912 ms
4rekdkeks.jpg
972 ms
petergof.jpg
1026 ms
most.jpg
1043 ms
prog1m.jpg
1106 ms
prog2m.jpg
1123 ms
dost1.jpg
1133 ms
all.js
25 ms
dost14.jpg
1132 ms
ca-pub-9793478593253120.js
57 ms
zrt_lookup.html
52 ms
show_ads_impl.js
57 ms
context.js
235 ms
p
88 ms
bykZquEtar47MWacwqm_6l.js
12 ms
ads
283 ms
opensearch.js
45 ms
muzrus1_p.jpg
1017 ms
muzetno1_p.jpg
1035 ms
p2.jpg
1096 ms
osd.js
18 ms
p1.jpg
1228 ms
yandex-hint-rb.png
35 ms
search.png
34 ms
v2
54 ms
dpx
5 ms
p3.jpg
1013 ms
p4.jpg
1013 ms
p5.jpg
1030 ms
context_static_r1065.js
336 ms
p6.jpg
1060 ms
xrefid.xgi
4 ms
52154.gif
5 ms
navbg.png
998 ms
newzag.png
1010 ms
newbg.png
1010 ms
12363396593139659504
48 ms
abg.js
51 ms
m_js_controller.js
59 ms
googlelogo_color_112x36dp.png
35 ms
newbot.png
971 ms
s
21 ms
x_button_blue2.png
22 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
4 ms
menubg.jpg
908 ms
arrow.png
972 ms
88232
160 ms
watch.js
207 ms
y150
24 ms
4rektop.png
687 ms
4rekbg.png
701 ms
4rekzag.png
704 ms
butbg.png
729 ms
4rekbot.png
755 ms
y90
18 ms
watch.js
462 ms
y150
8 ms
y90
6 ms
y150
12 ms
foothorse1.jpg
781 ms
footbg.jpg
786 ms
foothorse2.jpg
791 ms
mainmyli.php
474 ms
hit
253 ms
watch.js
619 ms
b-share.png
9 ms
footbg2.jpg
777 ms
b-share-icon.png
10 ms
b-share-popup_down__tail.png
13 ms
advert.gif
251 ms
upload.gif
258 ms
widget_comments.php
468 ms
counter
316 ms
activeview
17 ms
1
91 ms
9624157
94 ms
26812653
98 ms
loader_nav19127_3.js
130 ms
lite.css
255 ms
lite.js
517 ms
lang3_0.js
259 ms
widget_comments.css
263 ms
xdm.js
263 ms
al_comments.js
642 ms
--BaKE7L7G8.jpg
259 ms
KeBOtBBGVro.jpg
390 ms
bzjLG-LjuUg.jpg
386 ms
S9NDYdGM0BI.jpg
397 ms
nQpaUxAij18.jpg
401 ms
e_6531f428.jpg
407 ms
82-Idh_ZXx4.jpg
389 ms
b4beXOVZ5lQ.jpg
387 ms
deactivated_50.png
134 ms
w_comments_logo.png
131 ms
button_bgf.png
127 ms
statusx_op.gif
130 ms
like.gif
134 ms
q_frame.php
388 ms
AE6l7gZFHoW40000gQ00022ElWrIRGM5c8eLdh400004klLxJwHYK3zj3f6tiL6t1vDKhkz_GasGW3hFiBqeSaa3mV__________3tW8=v8VOJPK2cm5kGxS2YRhB44u1c5YAeLKwpRsimD6RfQvN70A8le2LiGIcIfsgmOW6Zxy6UCq2dx0t-5m6cGwWaF8hhv0G9zcGr32KcwuFfulogA27XXf1iG6oe5800hcgmOW6nOyFpQbS9AxEe0v9dzB__________m_J__________yFmW1w4000=mMTrEfK2cm5kGxS2CecLd2MOM8gmIpPm0RspnTYt0QMfsyu3YBEePv04faYTejhd18-_1dZD0f-mD_XS1faEe92z7w-G5n7Pa2uYb9yT3AUMaWAee3PMXq6n0RAWKW02kQBQvmJDlqesS07EkWQR4mBI__________yFq___________3y80Un00
116 ms
peterburg.biz accessibility score
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
Form elements do not have associated labels
Links do not have a discernible name
<object> elements do not have alternate text
peterburg.biz 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
peterburg.biz 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
Document uses plugins
RU
N/A
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Peterburg.biz 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 Peterburg.biz 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.
peterburg.biz
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: