Tools & Wizards About Us
wiki.servoy.com screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    67% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 62

    SEO

    Google-friendlier than
    22% of websites

wiki.servoy.com

Servoy Documentation - Documentation Home - Servoy Wiki

Page Load Speed

5.5 sec in total

First Response

476 ms

Resources Loaded

4.9 sec

Page Rendered

118 ms

wiki.servoy.com screenshot

About Website

Welcome to wiki.servoy.com homepage info - get ready to check Wiki Servoy best content for United States right away, or after learning these important things about wiki.servoy.com

Visit wiki.servoy.com

Key Findings

We analyzed Wiki.servoy.com page load time and found that the first response time was 476 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

wiki.servoy.com performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

69/100

10%

LCP (Largest Contentful Paint)

Value2.5 s

90/100

25%

SI (Speed Index)

Value7.8 s

23/100

10%

TBT (Total Blocking Time)

Value2,370 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.04

99/100

15%

TTI (Time to Interactive)

Value17.4 s

4/100

10%

Network Requests Diagram

wiki.servoy.com

476 ms

Servoy+Documentation

602 ms

batch.css

605 ms

batch.css

530 ms

batch.css

266 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 90% of them (45 requests) were addressed to the original Wiki.servoy.com, 6% (3 requests) were made to Google-analytics.com and 4% (2 requests) were made to . The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Wiki.servoy.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 53.3 kB (62%)

Content Size

85.3 kB

After Optimization

32.0 kB

  • HTML
  • JavaScript

In fact, the total size of Wiki.servoy.com main page is 85.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. 25% of websites need less resources to load. HTML takes 64.3 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 53.2 kB

  • Original 64.3 kB
  • After minification 56.7 kB
  • After compression 11.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. This page needs HTML code to be minified as it can gain 7.6 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 53.2 kB or 83% of the original size.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 20.9 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.

Requests Breakdown

Number of requests can be reduced by 25 (56%)

Requests Now

45

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wiki.servoy.com

wiki.servoy.com

476 ms

Servoy+Documentation

Servoy+Documentation

602 ms

batch.css

batch.css

605 ms

batch.css

batch.css

530 ms

batch.css

batch.css

266 ms

batch.css

batch.css

269 ms

com.comalatech.workflow:workflowResources.css

com.comalatech.workflow:workflowResources.css

272 ms

confluence.macros.advanced:favpages-resources.css

confluence.macros.advanced:favpages-resources.css

273 ms

com.atlassian.confluence.plugins.confluence-highlight-actions:highlighting-experiment-resources.css

com.atlassian.confluence.plugins.confluence-highlight-actions:highlighting-experiment-resources.css

544 ms

confluence.extra.jira:web-resources-adg.css

confluence.extra.jira:web-resources-adg.css

527 ms

colors.css

colors.css

544 ms

custom.css

custom.css

547 ms

batch.js

batch.js

1469 ms

batch.js

batch.js

1337 ms

batch.js

batch.js

882 ms

batch.js

batch.js

794 ms

com.comalatech.workflow:workflowResources.js

com.comalatech.workflow:workflowResources.js

793 ms

confluence.macros.advanced:favpages-resources.js

confluence.macros.advanced:favpages-resources.js

865 ms

com.atlassian.confluence.plugins.confluence-highlight-actions:highlighting-experiment-resources.js

com.atlassian.confluence.plugins.confluence-highlight-actions:highlighting-experiment-resources.js

1064 ms

com.atlassian.mywork.mywork-confluence-host-plugin:mw-header-anchor.js

com.atlassian.mywork.mywork-confluence-host-plugin:mw-header-anchor.js

1059 ms

doc-theme.js

doc-theme.js

1130 ms

custom.css

custom.css

775 ms

confluence-logo.png

confluence-logo.png

336 ms

global.logo

global.logo

336 ms

red_padlock.png

red_padlock.png

336 ms

appswitcher

appswitcher

333 ms

atlassian-icons.woff

atlassian-icons.woff

312 ms

tree.png

tree.png

305 ms

vgrabber.gif

vgrabber.gif

556 ms

7 ms

4HQveFbgAAAAABAAAAAMbULpkAAAAAyTFXWQAAAADJNQ9c

4HQveFbgAAAAABAAAAAMbULpkAAAAAyTFXWQAAAADJNQ9c

7 ms

analytics.js

analytics.js

95 ms

i18n

i18n

536 ms

naturalchildren.action

naturalchildren.action

506 ms

com.atlassian.confluence.plugins.share-page

com.atlassian.confluence.plugins.share-page

502 ms

3604651

3604651

497 ms

com.atlassian.confluence.plugins.confluence-like

com.atlassian.confluence.plugins.confluence-like

496 ms

724 ms

com.atlassian.confluence.plugins.watch-button

com.atlassian.confluence.plugins.watch-button

733 ms

3604651

3604651

731 ms

panel-items

panel-items

728 ms

userpopup-shadows.png

userpopup-shadows.png

725 ms

b.png

b.png

728 ms

collect

collect

16 ms

com.atlassian.confluence.plugins.recently-viewed-plugin

com.atlassian.confluence.plugins.recently-viewed-plugin

883 ms

likes

likes

507 ms

comment-likes

comment-likes

509 ms

f9a09586e09a8c8265c1b25dc0039d

f9a09586e09a8c8265c1b25dc0039d

513 ms

batch.css

batch.css

103 ms

collect

collect

5 ms

Accessibility Review

wiki.servoy.com accessibility score

86

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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.

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 [lang] attribute

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

wiki.servoy.com best practices score

67

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

wiki.servoy.com SEO score

62

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wiki.servoy.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Wiki.servoy.com 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

wiki.servoy.com

Open Graph description is not detected on the main page of Wiki Servoy. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: