Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 87

    SEO

    Google-friendlier than
    66% of websites

twiki.org

TWiki.org - Temporarily Unavailable

Page Load Speed

54.8 sec in total

First Response

594 ms

Resources Loaded

31.3 sec

Page Rendered

23 sec

twiki.org screenshot

About Website

Visit twiki.org now to see the best up-to-date TWiki content for United States and also check out these interesting facts you probably never knew about twiki.org

A leading Enterprise 2.0 collaboration platform with 400+ extensions, used by 50,000 businesses, maintained by an active open source community for 10+ years.

Visit twiki.org

Key Findings

We analyzed Twiki.org page load time and found that the first response time was 594 ms and then it took 54.2 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

twiki.org performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

71/100

25%

SI (Speed Index)

Value5.3 s

58/100

10%

TBT (Total Blocking Time)

Value1,720 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.013

100/100

15%

TTI (Time to Interactive)

Value16.0 s

6/100

10%

Network Requests Diagram

twiki.org

594 ms

jquery.js

276 ms

behaviour.compressed.js

1110 ms

twikilib.js

1696 ms

twikiWindow.js

1638 ms

Our browser made a total of 158 requests to load all elements on the main page. We found that 81% of them (128 requests) were addressed to the original Twiki.org, 4% (7 requests) were made to Apis.google.com and 3% (4 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (11.1 sec) relates to the external source Static.xx.fbcdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (55%)

Content Size

2.4 MB

After Optimization

1.1 MB

In fact, the total size of Twiki.org main page is 2.4 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. 70% of websites need less resources to load. Javascripts take 918.7 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 63.0 kB

  • Original 82.1 kB
  • After minification 78.8 kB
  • After compression 19.1 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 63.0 kB or 77% of the original size.

Image Optimization

-10%

Potential reduce by 71.8 kB

  • Original 705.4 kB
  • After minification 633.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. TWiki images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 608.9 kB

  • Original 918.7 kB
  • After minification 890.1 kB
  • After compression 309.8 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 608.9 kB or 66% of the original size.

CSS Optimization

-83%

Potential reduce by 569.5 kB

  • Original 685.1 kB
  • After minification 665.2 kB
  • After compression 115.6 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. Twiki.org needs all CSS files to be minified and compressed as it can save up to 569.5 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 63 (41%)

Requests Now

153

After Optimization

90

The browser has sent 153 CSS, Javascripts, AJAX and image requests in order to completely render the main page of TWiki. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

twiki.org accessibility score

71

Accessibility Issues

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.

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

<frame> or <iframe> elements do not have a title

High

Form elements do not have associated labels

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a valid value for its [lang] attribute.

Best Practices

twiki.org best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

twiki.org SEO score

87

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

Links do not have descriptive text

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 Twiki.org 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 Twiki.org 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 TWiki. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: