Tools & Wizards About Us
whatwedo.ch screenshot

Report Summary

  • 41

    Performance

    Renders faster than
    62% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 70% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    57% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

whatwedo.ch

whatwedo · Software Studio | Software Entwicklung Bern

Page Load Speed

3.6 sec in total

First Response

203 ms

Resources Loaded

3 sec

Page Rendered

416 ms

whatwedo.ch screenshot

About Website

Welcome to whatwedo.ch homepage info - get ready to check Whatwedo best content right away, or after learning these important things about whatwedo.ch

Wir digitalisieren Geschäftsideen auf Basis von modernen Technologien. Wir konzipieren und entwickeln Plattformen, E-Commerce, CMS und mehr…

Visit whatwedo.ch

Key Findings

We analyzed Whatwedo.ch page load time and found that the first response time was 203 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 55% of websites can load faster.

Performance Metrics

whatwedo.ch performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value9.3 s

1/100

25%

SI (Speed Index)

Value5.8 s

50/100

10%

TBT (Total Blocking Time)

Value710 ms

42/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value8.8 s

35/100

10%

Network Requests Diagram

whatwedo.ch

203 ms

whatwedo.ch

1296 ms

wp-emoji-release.min.js

109 ms

mediaelementplayer.min.css

213 ms

wp-mediaelement.css

288 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 72% of them (26 requests) were addressed to the original Whatwedo.ch, 11% (4 requests) were made to Use.typekit.net and 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Whatwedo.ch.

Page Optimization Overview & Recommendations

Page size can be reduced by 471.0 kB (13%)

Content Size

3.5 MB

After Optimization

3.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whatwedo.ch main page is 3.5 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. 40% of websites need less resources to load. Images take 3.1 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 45.9 kB

  • Original 54.1 kB
  • After minification 32.2 kB
  • After compression 8.2 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 21.9 kB, which is 40% 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 45.9 kB or 85% of the original size.

Image Optimization

-5%

Potential reduce by 149.0 kB

  • Original 3.1 MB
  • After minification 2.9 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. Whatwedo images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 247.5 kB

  • Original 389.5 kB
  • After minification 389.3 kB
  • After compression 142.1 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 247.5 kB or 64% of the original size.

CSS Optimization

-81%

Potential reduce by 28.6 kB

  • Original 35.4 kB
  • After minification 34.5 kB
  • After compression 6.8 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. Whatwedo.ch needs all CSS files to be minified and compressed as it can save up to 28.6 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (50%)

Requests Now

30

After Optimization

15

  • Images
  • JavaScript
  • CSS

The browser has sent 30 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whatwedo. 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 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

whatwedo.ch

whatwedo.ch

203 ms

whatwedo.ch

whatwedo.ch

1296 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

109 ms

mediaelementplayer.min.css

mediaelementplayer.min.css

213 ms

wp-mediaelement.css

wp-mediaelement.css

288 ms

jquery.js

jquery.js

398 ms

jquery-migrate.min.js

jquery-migrate.min.js

334 ms

iframeResizer.min.js

iframeResizer.min.js

309 ms

iframeResizer.contentWindow.min.js

iframeResizer.contentWindow.min.js

308 ms

ajp1euj.js

ajp1euj.js

248 ms

initial.css

initial.css

315 ms

whatwedo.ch

whatwedo.ch

469 ms

whatwedo.ch

whatwedo.ch

468 ms

css

css

64 ms

initial.js

initial.js

631 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

536 ms

wp-mediaelement.js

wp-mediaelement.js

465 ms

analytics.js

analytics.js

30 ms

collect

collect

15 ms

whatwedo.ch

whatwedo.ch

124 ms

whatwedo-logo-RGB-Copy-341x114-81921.png

whatwedo-logo-RGB-Copy-341x114-81921.png

321 ms

Group-1284x1492-58662.png

Group-1284x1492-58662.png

320 ms

Screenshot-2015-07-27-17.14.48-2376x1896-76296.png

Screenshot-2015-07-27-17.14.48-2376x1896-76296.png

1091 ms

mobile-devices-icons-Layout-1100x553-83983.png

mobile-devices-icons-Layout-1100x553-83983.png

176 ms

whatwedo-logo-RGB-Copy-300x100-76164.png

whatwedo-logo-RGB-Copy-300x100-76164.png

200 ms

1-2.jpg

1-2.jpg

669 ms

1-3.jpg

1-3.jpg

476 ms

1-1.jpg

1-1.jpg

384 ms

ueli1-1200x720-19877.png

ueli1-1200x720-19877.png

680 ms

rene1-1200x720-43407.png

rene1-1200x720-43407.png

567 ms

felix2-1200x720-16712.png

felix2-1200x720-16712.png

768 ms

IQHow_FEYlDC4Gzy_m8fcvEr6Hm6RMS0v1dtXsGir4g.ttf

IQHow_FEYlDC4Gzy_m8fcvEr6Hm6RMS0v1dtXsGir4g.ttf

33 ms

zhcz-_WihjSQC0oHJ9TCYC3USBnSvpkopQaUR-2r7iU.ttf

zhcz-_WihjSQC0oHJ9TCYC3USBnSvpkopQaUR-2r7iU.ttf

36 ms

mSaftagyRPLIEpo7jslKB2r1eyQALk2t44-gmj0PJrwff5WyggMdeMJ6Mk6g5Mofb29XZ2Sh5QjUFR6ujQZRZRBKwDIoF2Bqw2qXwRqDFDMhjRSk52JXwcB8wDbojDb3jcFcwDjujQMXjcB8wRmKZQI.woff

mSaftagyRPLIEpo7jslKB2r1eyQALk2t44-gmj0PJrwff5WyggMdeMJ6Mk6g5Mofb29XZ2Sh5QjUFR6ujQZRZRBKwDIoF2Bqw2qXwRqDFDMhjRSk52JXwcB8wDbojDb3jcFcwDjujQMXjcB8wRmKZQI.woff

210 ms

CkVFcN5nQv9Fg9P7DbtTnzoaAHJpB_nancDCK2l4huMff5dyggMdeMJ6Mk6g5Msfb29XZ2Sh5QjUFR6ujQZRZRBKwDIoF2Bqw2qXwRqDFDMhjRSk52JXwcB8wDbojDb3jcFcwDjujQMXjcB8wRmKZQI.woff

CkVFcN5nQv9Fg9P7DbtTnzoaAHJpB_nancDCK2l4huMff5dyggMdeMJ6Mk6g5Msfb29XZ2Sh5QjUFR6ujQZRZRBKwDIoF2Bqw2qXwRqDFDMhjRSk52JXwcB8wDbojDb3jcFcwDjujQMXjcB8wRmKZQI.woff

300 ms

p.gif

p.gif

182 ms

Accessibility Review

whatwedo.ch accessibility score

88

Accessibility Issues

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

Image elements do not have [alt] attributes

Best Practices

whatwedo.ch 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

whatwedo.ch SEO score

92

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

Image elements do not have [alt] attributes

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

    DE

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

whatwedo.ch

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