Tools & Wizards About Us

Report Summary

  • 28

    Performance

    Renders faster than
    47% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

witty.works

Witty: Scale inclusion faster. With language.

Page Load Speed

8.8 sec in total

First Response

2 sec

Resources Loaded

5.5 sec

Page Rendered

1.3 sec

About Website

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.works

Key Findings

We 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.

Performance Metrics

witty.works performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value8.5 s

2/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value1,340 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0.012

100/100

15%

TTI (Time to Interactive)

Value12.4 s

15/100

10%

Network Requests Diagram

www.witty.works

1981 ms

aos.js

27 ms

aos.css

36 ms

main.css

140 ms

theme-overrides.min.css

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 Optimization Overview & Recommendations

Page size can be reduced by 242.5 kB (30%)

Content Size

821.9 kB

After Optimization

579.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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.

HTML Optimization

-89%

Potential reduce by 221.7 kB

  • Original 248.7 kB
  • After minification 218.4 kB
  • After compression 26.9 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.

Image Optimization

-1%

Potential reduce by 6.4 kB

  • Original 493.1 kB
  • After minification 486.7 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.

JavaScript Optimization

-12%

Potential reduce by 6.2 kB

  • Original 51.2 kB
  • After minification 51.2 kB
  • After compression 45.0 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.

CSS Optimization

-28%

Potential reduce by 8.2 kB

  • Original 28.9 kB
  • After minification 28.9 kB
  • After compression 20.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. 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.

Requests Breakdown

Number of requests can be reduced by 24 (24%)

Requests Now

98

After Optimization

74

  • Images
  • JavaScript
  • CSS

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.

Network Requests Diagram

Accessibility Review

witty.works accessibility score

89

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

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

Heading elements are not in a sequentially-descending order

Best Practices

witty.works 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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

witty.works SEO score

91

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

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

Social Sharing Optimization

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: