6.5 sec in total
507 ms
5.5 sec
461 ms
Welcome to grandpetersburg.com homepage info - get ready to check Grand Petersburg best content right away, or after learning these important things about grandpetersburg.com
Shore excursions or city tours with «GrandPetersburg» tour operator! Private tours and shore excursions for cruise passengers around Russia and Scandinavia!
Visit grandpetersburg.comWe analyzed Grandpetersburg.com page load time and found that the first response time was 507 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
grandpetersburg.com performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value11.3 s
0/100
25%
Value10.3 s
8/100
10%
Value1,380 ms
16/100
30%
Value0
100/100
15%
Value13.0 s
13/100
10%
507 ms
1658 ms
253 ms
394 ms
411 ms
Our browser made a total of 107 requests to load all elements on the main page. We found that 78% of them (83 requests) were addressed to the original Grandpetersburg.com, 7% (7 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Tripadvisor.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Grandpetersburg.com.
Page size can be reduced by 109.3 kB (6%)
1.8 MB
1.7 MB
In fact, the total size of Grandpetersburg.com main page is 1.8 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 1.2 MB which makes up the majority of the site volume.
Potential reduce by 86.4 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 86.4 kB or 82% of the original size.
Potential reduce by 3.4 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. Grand Petersburg images are well optimized though.
Potential reduce by 3.3 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. This website has mostly compressed JavaScripts.
Potential reduce by 16.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. Grandpetersburg.com needs all CSS files to be minified and compressed as it can save up to 16.2 kB or 12% of the original size.
Number of requests can be reduced by 60 (64%)
94
34
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Grand Petersburg. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
grandpetersburg.com
507 ms
www.grandpetersburg.com
1658 ms
wp-emoji-release.min.js
253 ms
styles.css
394 ms
settings.css
411 ms
animation.css
535 ms
jquery-ui-1.8.24.custom.css
608 ms
magnific-popup.css
606 ms
flexslider.css
605 ms
mediaelementplayer.min.css
605 ms
tooltipster.css
551 ms
parallax.min.css
675 ms
supersized.css
691 ms
odometer-theme-minimal.css
746 ms
screen.css
944 ms
slick.css
747 ms
jquery.fancybox.css
880 ms
main.css
817 ms
bootstrap-grid.css
835 ms
font-awesome.min.css
888 ms
custom-css.php
891 ms
css
33 ms
grid.css
963 ms
jquery.js
1122 ms
jquery-migrate.min.js
1087 ms
jquery.themepunch.tools.min.js
1166 ms
jquery.themepunch.revolution.min.js
1167 ms
simple-facebook-page-root.js
1087 ms
box-shortcodes.css
1005 ms
jquery.form.min.js
1188 ms
scripts.js
1128 ms
jivosite-public.js
1149 ms
js
53 ms
parallax.min.js
1165 ms
jquery.easing.js
1206 ms
jquery.magnific-popup.js
1207 ms
waypoints.min.js
1275 ms
jquery.isotope.js
1291 ms
jquery.masory.js
1308 ms
jquery.tooltipster.min.js
1331 ms
wejs
38 ms
custom_plugins.js
1204 ms
custom.js
1063 ms
slick.js
1114 ms
popups.js
1006 ms
jquery.fancybox.js
1006 ms
dropdown.js
979 ms
ui.js
992 ms
wp-embed.min.js
990 ms
reset.css
722 ms
wordpress.css
735 ms
dummy.png
215 ms
sdk.js
88 ms
150_logo-11900-2.png
59 ms
logo_white.jpeg
158 ms
logo_white.jpg
159 ms
email.png
159 ms
top.png
210 ms
icon-fb-blue.svg
158 ms
icon-sp-blue.svg
365 ms
icon-inst.svg
364 ms
youtube.png
365 ms
Peter-and-Paul-Forstress-560x460.jpg
471 ms
IMG_7932-560x460.jpg
478 ms
20130406274-560x460.jpg
366 ms
IMG_7238-560x460.jpg
506 ms
Header-Summer-Palace-no-author-2-560x460.jpg
638 ms
sunday-twilight3-560x460.jpg
505 ms
The-Hermitage-and-Palace-Square-2-no-author-1-560x460.jpg
507 ms
Cathedral-of-Savior-on-the-Spilled-Blood-St.-Petersburg-560x460.jpg
746 ms
The-Catherine-Palace-in-Tsarskoe-Selo-St.-Petersburg-560x460.jpg
753 ms
logo_black.jpg
595 ms
1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4WjMDr4fJg.woff
69 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCFPrc.woff
100 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCFPrc.woff
169 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCFPrc.woff
132 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCFPrc.woff
140 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCFPrc.woff
141 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCFPrc.woff
188 ms
fontawesome-webfont.woff
775 ms
sdk.js
13 ms
WidgetEmbed-selfserveprop
94 ms
385gE8BhOE
676 ms
128 ms
t4b_widget_self_serve_property-v24221562771a.css
32 ms
cdswidgets_m-c-v22480917520a.js
63 ms
icon-search.svg
376 ms
analytics.js
95 ms
revolution.extension.carousel.min.js
481 ms
revolution.extension.layeranimation.min.js
487 ms
revolution.extension.navigation.min.js
492 ms
revolution.extension.parallax.min.js
587 ms
www.grandpetersburg.com
827 ms
www.grandpetersburg.com
876 ms
www.grandpetersburg.com
874 ms
ajax-loader.gif
617 ms
collect
13 ms
385gE8BhOE
594 ms
sunday-twilight3-e1527534444878.jpg
410 ms
Header-Kremlin-no-author-2.jpg
411 ms
IMG_7931.jpg
277 ms
openhand.cur
293 ms
revicons.woff
339 ms
DSC_7913-as-Smart-Object-1-small-768x511-1.jpg
278 ms
Tripadvisor_lockup_horizontal_secondary_registered-11900-2.svg
31 ms
mMYqt28Cv1
179 ms
TripAdvisor_Regular.woff
11 ms
grandpetersburg.com accessibility score
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
Buttons do not have an accessible name
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
Definition list items are not wrapped in <dl> elements
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
grandpetersburg.com 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
General
Impact
Issue
Detected JavaScript libraries
grandpetersburg.com 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Grandpetersburg.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Grandpetersburg.com 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.
grandpetersburg.com
Open Graph description is not detected on the main page of Grand Petersburg. 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: