6.6 sec in total
724 ms
3.9 sec
2 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 724 ms and then it took 5.9 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
Value4.3 s
18/100
10%
Value8.7 s
1/100
25%
Value6.1 s
44/100
10%
Value1,130 ms
22/100
30%
Value0
100/100
15%
Value14.0 s
10/100
10%
724 ms
35 ms
49 ms
217 ms
430 ms
Our browser made a total of 111 requests to load all elements on the main page. We found that 88% of them (98 requests) were addressed to the original Witty.works, 5% (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 (1.2 sec) belongs to the original domain Witty.works.
Page size can be reduced by 285.7 kB (12%)
2.3 MB
2.1 MB
In fact, the total size of Witty.works main page is 2.3 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. 55% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 264.3 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 34.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 264.3 kB or 89% of the original size.
Potential reduce by 7.0 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%)
102
78
The browser has sent 102 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
724 ms
aos.js
35 ms
aos.css
49 ms
main.css
217 ms
theme-overrides.min.css
430 ms
module_44020820179_Elements_-_Menu.min.css
439 ms
module_44020857063_Elements_-_Header_Search.min.css
441 ms
_carousel.min.css
463 ms
module_44020820414_Elements_-_Logo_Bar.min.css
463 ms
_video.min.css
461 ms
module_44020820415_Elements_-_Video.min.css
615 ms
module_44020933318_Elements_-_Carousel_-_Testimonial.min.css
679 ms
js
81 ms
style-overrides.min.css
633 ms
embed.js
558 ms
main.min.js
793 ms
jquery.min.js
660 ms
project.js
790 ms
module_44020820179_Elements_-_Menu.min.js
793 ms
carousel.min.js
795 ms
video.min.js
856 ms
24904016.js
845 ms
index.js
794 ms
play.svg
105 ms
facebook.svg
80 ms
twitter.svg
79 ms
instagram.svg
79 ms
linkedin.svg
79 ms
youtube.svg
79 ms
witty-logo-color-email.png
107 ms
bg-prod-pichi@1x.jpg
380 ms
witty-tiles-1.jpg
382 ms
van-tay-media-TFFn3BYLc5s-unspla.jpg
381 ms
desola-lanre-ologun-IgUR1iX0mqM-.jpg
384 ms
krakenimages-376KN_ISplE-unsplas.jpg
385 ms
gradient-linear-1920x1080.png
459 ms
Patagonia-1.png
533 ms
Haworth-1.png
381 ms
3-Apr-16-2024-08-49-53-2588-AM.png
614 ms
VBS-1.png
722 ms
1-Apr-16-2024-08-49-15-7970-AM.png
459 ms
Advantagegroup.png
616 ms
Riverside%20Logo.png
753 ms
masonbreese%20logo-1.png
614 ms
Infineon%20Logo.png
614 ms
Publicis%20Group%20Logo.png
738 ms
logo-partner-personio.webp
741 ms
logo-microsoft.svg
738 ms
logo-deutsche-bahn.svg
740 ms
Beekeeper%20Logo.png
742 ms
Miebach%20Consulting.png
841 ms
Wiener%20Wohnen%20Kundenservice.png
1007 ms
GEO%2BING%20logo.png
1033 ms
step-1_1-1.gif
861 ms
step-3_1-1.gif
1035 ms
step-2_1-1.gif
890 ms
step---analytics.gif
1043 ms
Innovation%20Award%20Finalist%202024%20LVMH%20Accelerator%20Maison%20des%20Startups%20Station%20F.png
895 ms
2-Jun-03-2024-10-49-53-8222-AM.png
918 ms
4-Jun-03-2024-10-50-20-7624-AM.png
1202 ms
3-Jun-03-2024-10-50-06-5825-AM.png
1018 ms
Adeco%20%20Digital%20Inclusion%20Award.png
1061 ms
regular.woff
1076 ms
regular.woff
1211 ms
6-4.png
1018 ms
24904016.js
593 ms
24904016.js
650 ms
conversations-embed.js
572 ms
fb.js
539 ms
La%20Nuit%20de%20lInnovation%20RH-1.png
1018 ms
La%20Maison%20des%20Startups.png
923 ms
Screenshot%202024-06-11%20at%2012.49.05.png
1079 ms
Microsoft_Office_Word_(2019%E2%80%93present).svg.png
916 ms
Microsoft_Edge_logo_(2019).png
996 ms
Google_Chrome_icon_(September_2014).svg.png
1015 ms
soc2.png
990 ms
4-Dec-21-2023-01-52-03-4127-PM.png
970 ms
5-Dec-21-2023-01-52-25-9747-PM.png
999 ms
6-3.png
901 ms
7-3.png
935 ms
A-groupe-of-diverse-people-in-a-business-context.webp
958 ms
An-asian-woman-talking-to-a-Afro-American-woman.webp
1034 ms
3%20diverse%20people%20looking%20at%20an%20ipad%20(1)%20(1).webp
843 ms
Alexander%20Haldemann.webp
899 ms
1-Dec-19-2022-02-17-04-3480-PM.png
896 ms
Louise%20Willoughby.jpeg
927 ms
Isabella%20Stampfli.jpeg
941 ms
Christian%20Langenegger.webp
930 ms
4-Dec-19-2022-02-16-48-6090-PM.png
1241 ms
lena%20stelzner.webp
987 ms
2-Dec-19-2022-02-16-30-4439-PM.png
1119 ms
1667403002661.jpeg
925 ms
Microsoft_logo_(2012).svg.png
1047 ms
marion-riesinger.webp
814 ms
3-Dec-19-2022-02-16-02-5188-PM.png
997 ms
Lucie%20Schibel.jpeg
875 ms
Berlin%20University%20Alliance.jpeg
857 ms
Matthias%20Becker.jpeg
951 ms
Dr%20Weber%20Partner.png
986 ms
mobatime.png
944 ms
Portrait%20of%20diverse%20people%20and%20the%20Hashtag%20%23LanguageMatters.webp
953 ms
bias-_bias-classicism_bias-ethnicity.webp
943 ms
bias-_bias-classicism_bias-gender.webp
904 ms
bias-age.svg
815 ms
bias-_bias-classicism_bias-classism.webp
841 ms
bias-_bias-classicism_bias-faith.webp
843 ms
bias-_bias-classicism_bias-orientation.webp
848 ms
bias-_bias-classicism_bias-disability.webp
818 ms
bias-_bias-classicism_bias-other.webp
808 ms
gradient-mesh-1920x1080-1.webp
801 ms
soc2.png
840 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
Browser errors were logged to the console
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: