Tools & Wizards About Us
princess.ch screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

princess.ch

Food- & Reiseblog aus der Schweiz - Princess.ch

Page Load Speed

5.3 sec in total

First Response

462 ms

Resources Loaded

3.1 sec

Page Rendered

1.8 sec

princess.ch screenshot

About Website

Visit princess.ch now to see the best up-to-date Princess content for Russia and also check out these interesting facts you probably never knew about princess.ch

Princess.ch ist ein Schweizer Foodblog & Travel-Blog seit 2009. Es dreht sich um Ausflugsziele, Reise-Tipps, Rezepte, Restaurant-Empfehlungen und Food-Trends.

Visit princess.ch

Key Findings

We analyzed Princess.ch page load time and found that the first response time was 462 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

princess.ch performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

24/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

34/100

25%

SI (Speed Index)

Value6.6 s

38/100

10%

TBT (Total Blocking Time)

Value470 ms

60/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.5 s

30/100

10%

Network Requests Diagram

princess.ch

462 ms

princess.ch

453 ms

250 ms

be334334bd29701163a576d716a22fa1.css

234 ms

css

36 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that 57% of them (13 requests) were addressed to the original Princess.ch, 17% (4 requests) were made to A.mailmunch.co and 9% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (650 ms) belongs to the original domain Princess.ch.

Page Optimization Overview & Recommendations

Page size can be reduced by 177.6 kB (29%)

Content Size

608.3 kB

After Optimization

430.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Princess.ch main page is 608.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Javascripts take 221.0 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 175.3 kB

  • Original 209.7 kB
  • After minification 203.8 kB
  • After compression 34.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 175.3 kB or 84% of the original size.

Image Optimization

-1%

Potential reduce by 916 B

  • Original 112.4 kB
  • After minification 111.5 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. Princess images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 984 B

  • Original 221.0 kB
  • After minification 221.0 kB
  • After compression 220.0 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

-1%

Potential reduce by 469 B

  • Original 65.2 kB
  • After minification 65.2 kB
  • After compression 64.7 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. Princess.ch has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 12 (63%)

Requests Now

19

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 19 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Princess. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

princess.ch

princess.ch

462 ms

princess.ch

princess.ch

453 ms

250 ms

be334334bd29701163a576d716a22fa1.css

be334334bd29701163a576d716a22fa1.css

234 ms

css

css

36 ms

css

css

53 ms

jquery.min.js

jquery.min.js

346 ms

site.js

site.js

20 ms

gtm4wp-contact-form-7-tracker.js

gtm4wp-contact-form-7-tracker.js

499 ms

gtm4wp-form-move-tracker.js

gtm4wp-form-move-tracker.js

498 ms

e-202430.js

e-202430.js

18 ms

f14f9c2a33fd2b3b6924ba142f79d384.js

f14f9c2a33fd2b3b6924ba142f79d384.js

650 ms

gtm.js

gtm.js

185 ms

sbi-sprite.png

sbi-sprite.png

210 ms

Logo2020_sw.png

Logo2020_sw.png

210 ms

Ausflugsziele-Meiringen-Hasliberg-Brienzersee-25-850x567.jpg

Ausflugsziele-Meiringen-Hasliberg-Brienzersee-25-850x567.jpg

542 ms

jquery.min.js

jquery.min.js

121 ms

ts-icons.woff

ts-icons.woff

318 ms

styles.css

styles.css

6 ms

179933

179933

36 ms

settings-1721670324.json

settings-1721670324.json

3 ms

scrollbox.js

scrollbox.js

2 ms

a024cb24f300d323f20445974d4bf0f7.js

a024cb24f300d323f20445974d4bf0f7.js

224 ms

Accessibility Review

princess.ch accessibility score

93

Accessibility Issues

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best Practices

princess.ch best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

princess.ch SEO score

90

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Princess.ch can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Princess.ch 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

princess.ch

Open Graph data is detected on the main page of Princess. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: