Tools & Wizards About Us
mountain.partners screenshot

Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

mountain.partners

Mountain Partners

Page Load Speed

2.3 sec in total

First Response

288 ms

Resources Loaded

1.8 sec

Page Rendered

265 ms

mountain.partners screenshot

About Website

Visit mountain.partners now to see the best up-to-date Mountain content for Switzerland and also check out these interesting facts you probably never knew about mountain.partners

Mountain Partners AG

Visit mountain.partners

Key Findings

We analyzed Mountain.partners page load time and found that the first response time was 288 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

mountain.partners performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

60/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

10/100

25%

SI (Speed Index)

Value7.4 s

27/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.5 s

71/100

10%

Network Requests Diagram

mountain.partners

288 ms

mountain.partners

475 ms

app.bundle.css

222 ms

css

28 ms

app.bundle.js

634 ms

Our browser made a total of 10 requests to load all elements on the main page. We found that 60% of them (6 requests) were addressed to the original Mountain.partners, 30% (3 requests) were made to Fonts.gstatic.com and 10% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Mountain.partners.

Page Optimization Overview & Recommendations

Page size can be reduced by 94.5 kB (33%)

Content Size

290.5 kB

After Optimization

196.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mountain.partners main page is 290.5 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. 15% of websites need less resources to load. Javascripts take 224.8 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 27.8 kB

  • Original 34.7 kB
  • After minification 29.5 kB
  • After compression 6.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. This page needs HTML code to be minified as it can gain 5.2 kB, which is 15% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 27.8 kB or 80% of the original size.

Image Optimization

-25%

Potential reduce by 90 B

  • Original 358 B
  • After minification 268 B

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. Obviously, Mountain needs image optimization as it can save up to 90 B or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-25%

Potential reduce by 56.2 kB

  • Original 224.8 kB
  • After minification 224.8 kB
  • After compression 168.6 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 56.2 kB or 25% of the original size.

CSS Optimization

-34%

Potential reduce by 10.4 kB

  • Original 30.7 kB
  • After minification 30.7 kB
  • After compression 20.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. Mountain.partners needs all CSS files to be minified and compressed as it can save up to 10.4 kB or 34% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

5

After Optimization

5

  • Images
  • JavaScript
  • CSS

The browser has sent 5 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mountain. According to our analytics all requests are already optimized.

Network Requests Diagram

mountain.partners

mountain.partners

288 ms

mountain.partners

mountain.partners

475 ms

app.bundle.css

app.bundle.css

222 ms

css

css

28 ms

app.bundle.js

app.bundle.js

634 ms

loading-logo.gif

loading-logo.gif

1011 ms

close-cursor.png

close-cursor.png

178 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

33 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

47 ms

MjQDmil5tffhpBrklnWOaJaiuA.ttf

MjQDmil5tffhpBrklnWOaJaiuA.ttf

48 ms

Accessibility Review

mountain.partners accessibility score

79

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

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

High

<html> element does not have a [lang] attribute

Best Practices

mountain.partners best practices score

92

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

Missing source maps for large first-party JavaScript

SEO Factors

mountain.partners SEO score

83

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

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mountain.partners can be misinterpreted by Google and other search engines. Our service has detected that English 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 Mountain.partners 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

mountain.partners

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