8.8 sec in total
2 sec
5.5 sec
1.3 sec
Welcome to witty.works homepage info - get ready to check Witty best content right away, or after learning these important things about witty.works
Operationalize inclusion across your organization in a few hours, increasing employee loyalty by over 35%. With a simple tool: Language.
Visit witty.worksWe analyzed Witty.works page load time and found that the first response time was 2 sec and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
witty.works performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value8.5 s
2/100
25%
Value8.1 s
21/100
10%
Value1,340 ms
17/100
30%
Value0.012
100/100
15%
Value12.4 s
15/100
10%
1981 ms
27 ms
36 ms
140 ms
270 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 84% of them (85 requests) were addressed to the original Witty.works, 6% (6 requests) were made to F.hubspotusercontent10.net and 2% (2 requests) were made to Unpkg.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Witty.works.
Page size can be reduced by 242.5 kB (30%)
821.9 kB
579.4 kB
In fact, the total size of Witty.works main page is 821.9 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. 50% of websites need less resources to load. Images take 493.1 kB which makes up the majority of the site volume.
Potential reduce by 221.7 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.3 kB, which is 12% 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 221.7 kB or 89% of the original size.
Potential reduce by 6.4 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. Witty images are well optimized though.
Potential reduce by 6.2 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 6.2 kB or 12% of the original size.
Potential reduce by 8.2 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. Witty.works needs all CSS files to be minified and compressed as it can save up to 8.2 kB or 28% of the original size.
Number of requests can be reduced by 24 (24%)
98
74
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Witty. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
www.witty.works
1981 ms
aos.js
27 ms
aos.css
36 ms
main.css
140 ms
theme-overrides.min.css
270 ms
module_44020820179_Elements_-_Menu.min.css
377 ms
module_44020857063_Elements_-_Header_Search.min.css
369 ms
_video.min.css
421 ms
module_44020820415_Elements_-_Video.min.css
440 ms
_carousel.min.css
436 ms
module_44020820414_Elements_-_Logo_Bar.min.css
464 ms
module_44020933318_Elements_-_Carousel_-_Testimonial.min.css
540 ms
js
79 ms
style-overrides.min.css
492 ms
embed.js
40 ms
main.min.js
525 ms
jquery.min.js
732 ms
project.js
658 ms
module_44020820179_Elements_-_Menu.min.js
733 ms
video.min.js
732 ms
carousel.min.js
753 ms
24904016.js
513 ms
index.js
732 ms
play.svg
213 ms
facebook.svg
460 ms
twitter.svg
455 ms
instagram.svg
458 ms
linkedin.svg
457 ms
youtube.svg
456 ms
witty-logo-color-email.png
525 ms
bg-prod-pichi@1x.jpg
459 ms
witty-tiles-1.webp
454 ms
step-1_1-1.gif
456 ms
step-3_1-1.gif
527 ms
step-2_1-1.gif
525 ms
step---analytics.gif
658 ms
Advantagegroup.png
764 ms
Riverside%20Logo.png
763 ms
Schweizerische%20Eidgenossenschaft.png
765 ms
masonbreese%20logo-1.png
779 ms
Infineon%20Logo.png
780 ms
Publicis%20Group%20Logo.png
920 ms
Z%C3%BChlke%20logo.png
777 ms
canva%20logo.png
986 ms
logo-partner-personio.webp
1053 ms
forto-gmbh-logo-vector.png
872 ms
logo-microsoft.svg
869 ms
logo-deutsche-bahn.svg
884 ms
logo-deloitte.svg
965 ms
Greenpeace-logo.png
1164 ms
fossil%20logo.jpeg
1163 ms
Nike-Logo.png
1354 ms
4-Dec-21-2023-01-52-03-4127-PM.png
1094 ms
5-Dec-21-2023-01-52-25-9747-PM.png
1140 ms
6-3.png
1258 ms
7-3.png
1224 ms
A-groupe-of-diverse-people-in-a-business-context.webp
1414 ms
An-asian-woman-talking-to-a-Afro-American-woman.webp
1295 ms
3%20diverse%20people%20looking%20at%20an%20ipad%20(1)%20(1).webp
1201 ms
Alexander%20Haldemann.webp
1251 ms
landing
406 ms
1-Dec-19-2022-02-17-04-3480-PM.png
1417 ms
Christian%20Langenegger.webp
1431 ms
4-Dec-19-2022-02-16-48-6090-PM.png
1421 ms
regular.woff
1301 ms
24904016.js
667 ms
conversations-embed.js
589 ms
24904016.js
616 ms
fb.js
597 ms
regular.woff
1257 ms
lena%20stelzner.webp
1081 ms
2-Dec-19-2022-02-16-30-4439-PM.png
1278 ms
1667403002661.jpeg
1393 ms
Microsoft_logo_(2012).svg.png
1184 ms
marion-riesinger.webp
1153 ms
3-Dec-19-2022-02-16-02-5188-PM.png
1361 ms
Lucie%20Schibel.jpeg
1211 ms
Berlin%20University%20Alliance.jpeg
1205 ms
Matthias%20Becker.jpeg
1211 ms
Dr%20Weber%20Partner.png
1265 ms
mobatime.png
1355 ms
Google%20Docs%20Logo-1.png
1394 ms
Notion%20Logo.png
1465 ms
3-Nov-07-2022-12-27-43-6453-PM.png
1381 ms
linkedIn.png
1396 ms
Logo%20Personio.png
1464 ms
Greenhouse%20logo.png
1492 ms
iconizer-Install.png
1315 ms
icon-inclusive-tool.svg
1357 ms
illustration%20-%20hands%20inward@2x%20(1).png
1305 ms
icon%20-%20measure%20progress@2x.png
1282 ms
Portrait%20of%20diverse%20people%20and%20the%20Hashtag%20%23LanguageMatters.webp
1323 ms
bias-_bias-classicism_bias-ethnicity.webp
1458 ms
bias-_bias-classicism_bias-gender.webp
1281 ms
bias-age.svg
1452 ms
bias-_bias-classicism_bias-classism.webp
1418 ms
bias-_bias-classicism_bias-faith.webp
1466 ms
bias-_bias-classicism_bias-orientation.webp
1247 ms
bias-_bias-classicism_bias-disability.webp
1232 ms
bias-_bias-classicism_bias-other.webp
1293 ms
gradient-mesh-1920x1080-1.webp
1253 ms
witty.works accessibility score
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
Buttons do not have an accessible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
witty.works best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
witty.works SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Witty.works 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 Witty.works 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.
witty.works
Open Graph data is detected on the main page of Witty. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: