Tools & Wizards About Us

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

grandpetersburg.com

Shore Excursions and Private City Tours | GrandPetersburg

Page Load Speed

6.5 sec in total

First Response

507 ms

Resources Loaded

5.5 sec

Page Rendered

461 ms

About Website

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.com

Key Findings

We 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.

Performance Metrics

grandpetersburg.com performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

17/100

10%

LCP (Largest Contentful Paint)

Value11.3 s

0/100

25%

SI (Speed Index)

Value10.3 s

8/100

10%

TBT (Total Blocking Time)

Value1,380 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.0 s

13/100

10%

Network Requests Diagram

grandpetersburg.com

507 ms

www.grandpetersburg.com

1658 ms

wp-emoji-release.min.js

253 ms

styles.css

394 ms

settings.css

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 Optimization Overview & Recommendations

Page size can be reduced by 109.3 kB (6%)

Content Size

1.8 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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.

HTML Optimization

-82%

Potential reduce by 86.4 kB

  • Original 105.9 kB
  • After minification 96.6 kB
  • After compression 19.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 86.4 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 3.4 kB

  • Original 1.2 MB
  • After minification 1.2 MB

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.

JavaScript Optimization

-1%

Potential reduce by 3.3 kB

  • Original 308.1 kB
  • After minification 308.1 kB
  • After compression 304.8 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.

CSS Optimization

-12%

Potential reduce by 16.2 kB

  • Original 130.1 kB
  • After minification 128.9 kB
  • After compression 113.9 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.

Requests Breakdown

Number of requests can be reduced by 60 (64%)

Requests Now

94

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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.

Network Requests Diagram

Accessibility Review

grandpetersburg.com accessibility score

66

Accessibility Issues

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

High

Buttons do not have an accessible name

High

Form elements do not have associated labels

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

Definition list items are not wrapped in <dl> elements

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

grandpetersburg.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

grandpetersburg.com SEO score

100

Search Engine Optimization Advices

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    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.

Social Sharing Optimization

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: