4.9 sec in total
111 ms
4.3 sec
522 ms
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.chWe analyzed Whatwedo.ch page load time and found that the first response time was 111 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
whatwedo.ch performance score
name
value
score
weighting
Value2.4 s
70/100
10%
Value10.6 s
0/100
25%
Value11.4 s
5/100
10%
Value1,900 ms
8/100
30%
Value0
100/100
15%
Value11.5 s
18/100
10%
111 ms
1296 ms
600 ms
723 ms
987 ms
Our browser made a total of 40 requests to load all elements on the main page. We found that 58% of them (23 requests) were addressed to the original Whatwedo.ch, 38% (15 requests) were made to Graphql.whatwedo.ch and 5% (2 requests) were made to A.whatwedo.ch. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source A.whatwedo.ch.
Page size can be reduced by 144.6 kB (37%)
389.3 kB
244.7 kB
In fact, the total size of Whatwedo.ch main page is 389.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 213.9 kB which makes up the majority of the site volume.
Potential reduce by 138.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. 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 138.2 kB or 79% of the original size.
Potential reduce by 6.4 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.
Number of requests can be reduced by 6 (18%)
33
27
The browser has sent 33 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 7 to 1 for JavaScripts and as a result speed up the page load time.
whatwedo.ch
111 ms
www.whatwedo.ch
1296 ms
stv.svg
600 ms
polyfill-e912a8b0c652852ec988.js
723 ms
app-376a0ac9602ff83b2031.js
987 ms
dc6a8720040df98778fe970bf6c000a41750d3ae-a22b2e6ee9050863dd02.js
634 ms
framework-61364254349e8d23b6f5.js
845 ms
webpack-runtime-66466d1970ff0103f057.js
540 ms
oepfelchasper-01.svg
560 ms
gibb-01.svg
557 ms
wks-01.svg
579 ms
mw-ing.svg
567 ms
manuels-01.svg
1061 ms
berncity.svg
1081 ms
sensopro.svg
1050 ms
unibe-bern-01.svg
1048 ms
adrianos-01.svg
1077 ms
gemfloor-01.svg
1327 ms
snm-01.svg
1584 ms
bauhaus.svg
1490 ms
finesolutions-01.svg
1433 ms
6-3_Entwicklung.svg
520 ms
2_Digitalisierung-compass-grey.svg
1035 ms
3_Business-Analyse-graph-up-grey.svg
968 ms
instagram.svg
1081 ms
linkedin.svg
1207 ms
github.svg
1082 ms
Logo-Swissmade-sotware.svg
1476 ms
SLBronzePartner-vector_RVB_neg.svg
1501 ms
Logo-Gislerprotokoll-White.svg
1327 ms
DIN-neg-01.svg
1277 ms
Logo_swiss-ICT.svg
1718 ms
OTRGrotesk-Regular-bd08e8e78f2844112a9d4180b1a00a15.woff
1750 ms
OTRGrotesk-Medium-ba8ab0045f992eff52a2272013717763.woff
1477 ms
OTRGrotesk-SemiBold-9d1ab15a8bd4ddd8fe529da28f8b7620.woff
1594 ms
OTRGrotesk-Bold-c0b83cd64fe99e96f21da19b8bc0ca75.woff
1725 ms
piwik.js
657 ms
RobotoMono-Regular-418a8f9f65ccad0918afaf29822b460d.ttf
1815 ms
configs.php
2145 ms
1339 ms
whatwedo.ch accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
whatwedo.ch best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
whatwedo.ch SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
DE
DE
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 matches the claimed 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.
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: