Tools & Wizards About Us
group.pictet screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

group.pictet

Pictet US | Leading European independent investment firm

Page Load Speed

3.8 sec in total

First Response

367 ms

Resources Loaded

2.3 sec

Page Rendered

1.2 sec

group.pictet screenshot

About Website

Click here to check amazing Group content for Switzerland. Otherwise, check out these important facts you probably never knew about group.pictet

Pictet is specialised in wealth management, asset management & asset servicing. Discover how our 200+ years of global investment leadership can help you.

Visit group.pictet

Key Findings

We analyzed Group.pictet page load time and found that the first response time was 367 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

group.pictet performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value5.9 s

14/100

25%

SI (Speed Index)

Value15.6 s

0/100

10%

TBT (Total Blocking Time)

Value11,960 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value18.5 s

3/100

10%

Network Requests Diagram

group.pictet

367 ms

en

458 ms

clientlib-base.lc-e79fc59fc770363b352a984d2cca3c34-lc.min.css

27 ms

launch-1990ebcf3df6.min.js

201 ms

clientlib-site.lc-49126a0c86faf8478300078acf3b25f6-lc.min.css

114 ms

Our browser made a total of 18 requests to load all elements on the main page. We found that 6% of them (1 request) were addressed to the original Group.pictet, 78% (14 requests) were made to Pictet.com and 6% (1 request) were made to Assets.adobedtm.com. The less responsive or slowest element that took the longest time to load (511 ms) relates to the external source Pictet.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 114.3 kB (74%)

Content Size

154.4 kB

After Optimization

40.1 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Group.pictet main page is 154.4 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. HTML takes 131.3 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 113.7 kB

  • Original 131.3 kB
  • After minification 100.8 kB
  • After compression 17.6 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 30.5 kB, which is 23% 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 113.7 kB or 87% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 19.6 kB
  • After minification 19.6 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. Group images are well optimized though.

CSS Optimization

-16%

Potential reduce by 571 B

  • Original 3.5 kB
  • After minification 3.5 kB
  • After compression 2.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. Group.pictet needs all CSS files to be minified and compressed as it can save up to 571 B or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (33%)

Requests Now

12

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

group.pictet

group.pictet

367 ms

en

en

458 ms

clientlib-base.lc-e79fc59fc770363b352a984d2cca3c34-lc.min.css

clientlib-base.lc-e79fc59fc770363b352a984d2cca3c34-lc.min.css

27 ms

launch-1990ebcf3df6.min.js

launch-1990ebcf3df6.min.js

201 ms

clientlib-site.lc-49126a0c86faf8478300078acf3b25f6-lc.min.css

clientlib-site.lc-49126a0c86faf8478300078acf3b25f6-lc.min.css

114 ms

core.wcm.components.commons.datalayer.v1.lc-904d3c2f1e821ab45124d66de422b409-lc.min.js

core.wcm.components.commons.datalayer.v1.lc-904d3c2f1e821ab45124d66de422b409-lc.min.js

84 ms

clientlib-site.lc-0366f5f780f972748f36904cdd02b738-lc.min.js

clientlib-site.lc-0366f5f780f972748f36904cdd02b738-lc.min.js

195 ms

container.lc-0a6aff292f5cc42142779cde92054524-lc.min.js

container.lc-0a6aff292f5cc42142779cde92054524-lc.min.js

190 ms

clientlib-base.lc-12b8720c5ae214f9cecd41c78fd0bbd6-lc.min.js

clientlib-base.lc-12b8720c5ae214f9cecd41c78fd0bbd6-lc.min.js

78 ms

highcharts.css

highcharts.css

125 ms

logo_1.svg

logo_1.svg

219 ms

ZURICH-Leuenhof-office-DSC_6493_new%3Aimage-3-2

ZURICH-Leuenhof-office-DSC_6493_new%3Aimage-3-2

298 ms

logo_2.svg

logo_2.svg

182 ms

icon-link-arrow.svg

icon-link-arrow.svg

168 ms

LardySans-Regular.woff2

LardySans-Regular.woff2

33 ms

LardySans-Bold.woff2

LardySans-Bold.woff2

511 ms

LardySerif-Regular.woff2

LardySerif-Regular.woff2

34 ms

LardySerif-Bold.woff2

LardySerif-Bold.woff2

75 ms

Accessibility Review

group.pictet accessibility score

74

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

Image elements do not have [alt] attributes

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.

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

group.pictet best practices score

83

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

SEO Factors

group.pictet SEO score

79

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

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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 Group.pictet 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 Group.pictet 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

group.pictet

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