Tools & Wizards About Us
open-paas.org screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

open-paas.org

Home - OpenPaas Smart Open Source Digital Workplace

Page Load Speed

5.3 sec in total

First Response

249 ms

Resources Loaded

4.3 sec

Page Rendered

784 ms

open-paas.org screenshot

About Website

Visit open-paas.org now to see the best up-to-date Open Paas content for Finland and also check out these interesting facts you probably never knew about open-paas.org

OPENPAAS - SMART DIGITAL WORKPLACE - The Open-Source Alternative to Microsoft 365 & Google Suite - The complete collaboration suite

Visit open-paas.org

Key Findings

We analyzed Open-paas.org page load time and found that the first response time was 249 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

open-paas.org performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.9 s

1/100

10%

LCP (Largest Contentful Paint)

Value21.8 s

0/100

25%

SI (Speed Index)

Value18.3 s

0/100

10%

TBT (Total Blocking Time)

Value570 ms

52/100

30%

CLS (Cumulative Layout Shift)

Value0.156

74/100

15%

TTI (Time to Interactive)

Value23.4 s

1/100

10%

Network Requests Diagram

open-paas.org

249 ms

open-paas.org

1713 ms

style.min.css

262 ms

autoptimize_single_0bf4a4a101d33f5126c845c6ce648c09.css

328 ms

autoptimize_single_0e4a098f3f6e3faede64db8b9da80ba2.css

256 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 95% of them (72 requests) were addressed to the original Open-paas.org, 3% (2 requests) were made to Owa.linagora.com and 3% (2 requests) were made to Piwik.linagora.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Open-paas.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (69%)

Content Size

2.1 MB

After Optimization

644.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Open-paas.org main page is 2.1 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. 60% of websites need less resources to load. CSS take 839.8 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 207.4 kB

  • Original 241.7 kB
  • After minification 241.5 kB
  • After compression 34.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. 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 207.4 kB or 86% of the original size.

Image Optimization

-2%

Potential reduce by 5.2 kB

  • Original 254.6 kB
  • After minification 249.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. Open Paas images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 509.3 kB

  • Original 719.3 kB
  • After minification 718.7 kB
  • After compression 210.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 509.3 kB or 71% of the original size.

CSS Optimization

-82%

Potential reduce by 689.4 kB

  • Original 839.8 kB
  • After minification 838.8 kB
  • After compression 150.3 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. Open-paas.org needs all CSS files to be minified and compressed as it can save up to 689.4 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 57 (84%)

Requests Now

68

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

open-paas.org

open-paas.org

249 ms

open-paas.org

open-paas.org

1713 ms

style.min.css

style.min.css

262 ms

autoptimize_single_0bf4a4a101d33f5126c845c6ce648c09.css

autoptimize_single_0bf4a4a101d33f5126c845c6ce648c09.css

328 ms

autoptimize_single_0e4a098f3f6e3faede64db8b9da80ba2.css

autoptimize_single_0e4a098f3f6e3faede64db8b9da80ba2.css

256 ms

autoptimize_single_20e8490fab0dcf7557a5c8b54494db6f.css

autoptimize_single_20e8490fab0dcf7557a5c8b54494db6f.css

255 ms

autoptimize_single_359aca8a88b2331aa34ac505acad9911.css

autoptimize_single_359aca8a88b2331aa34ac505acad9911.css

339 ms

autoptimize_single_572161d751ca3b708cb5500fd5c61935.css

autoptimize_single_572161d751ca3b708cb5500fd5c61935.css

259 ms

zita-pro-min.css

zita-pro-min.css

424 ms

autoptimize_single_f794b6b888cf03343419a2fb3fd65e79.css

autoptimize_single_f794b6b888cf03343419a2fb3fd65e79.css

630 ms

autoptimize_single_c495654869785bc3df60216616814ad1.css

autoptimize_single_c495654869785bc3df60216616814ad1.css

432 ms

autoptimize_single_f6a56d06696888fae9a1588206ae41f3.css

autoptimize_single_f6a56d06696888fae9a1588206ae41f3.css

350 ms

autoptimize_single_1a337c353809f62263b53ba56a113324.css

autoptimize_single_1a337c353809f62263b53ba56a113324.css

412 ms

dashicons.min.css

dashicons.min.css

505 ms

elementor-icons.min.css

elementor-icons.min.css

438 ms

frontend.min.css

frontend.min.css

656 ms

swiper.min.css

swiper.min.css

507 ms

autoptimize_single_740d841c7f99319aa1638686930e90cc.css

autoptimize_single_740d841c7f99319aa1638686930e90cc.css

519 ms

autoptimize_single_953f94779f5ae871f5669c6b4bb84a71.css

autoptimize_single_953f94779f5ae871f5669c6b4bb84a71.css

529 ms

autoptimize_single_9ded3002a9e3d5b1f777fe7b89fb76da.css

autoptimize_single_9ded3002a9e3d5b1f777fe7b89fb76da.css

593 ms

fontawesome.min.css

fontawesome.min.css

675 ms

solid.min.css

solid.min.css

607 ms

regular.min.css

regular.min.css

617 ms

brands.min.css

brands.min.css

681 ms

jquery.min.js

jquery.min.js

780 ms

jquery-migrate.min.js

jquery-migrate.min.js

706 ms

autoptimize_single_dcf51362dbf808524435ddc49207d1e3.js

autoptimize_single_dcf51362dbf808524435ddc49207d1e3.js

710 ms

autoptimize_single_0996d9ad4ee79a52abcbfed9ac95f244.js

autoptimize_single_0996d9ad4ee79a52abcbfed9ac95f244.js

741 ms

autoptimize_single_dffa195b546cf1dfd52f2206955eb892.js

autoptimize_single_dffa195b546cf1dfd52f2206955eb892.js

762 ms

autoptimize_single_12095fd2f5c56f698eed65679fbedc1c.js

autoptimize_single_12095fd2f5c56f698eed65679fbedc1c.js

767 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

892 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

892 ms

autoptimize_single_26b4f0c3c1bcf76291fa4952fb7f04fb.css

autoptimize_single_26b4f0c3c1bcf76291fa4952fb7f04fb.css

892 ms

animations.min.css

animations.min.css

893 ms

autoptimize_single_6ce86c3105139cb3c80913e6a3696a96.js

autoptimize_single_6ce86c3105139cb3c80913e6a3696a96.js

893 ms

autoptimize_single_5bc2b1fa970f9cecb3c30c0c92c98271.js

autoptimize_single_5bc2b1fa970f9cecb3c30c0c92c98271.js

894 ms

autoptimize_single_43f25fdc5a2795336f5426e7985766bd.js

autoptimize_single_43f25fdc5a2795336f5426e7985766bd.js

895 ms

autoptimize_single_225f2a6345a416b2b21140e62bd652bd.js

autoptimize_single_225f2a6345a416b2b21140e62bd652bd.js

893 ms

autoptimize_single_2eab10bc950b6287e0f9a5f169a14ef0.js

autoptimize_single_2eab10bc950b6287e0f9a5f169a14ef0.js

714 ms

autoptimize_single_7b047b009e4f61d793513c8d3d9488a4.js

autoptimize_single_7b047b009e4f61d793513c8d3d9488a4.js

714 ms

autoptimize_single_52a482a8fdb25357e596ba08f323df27.js

autoptimize_single_52a482a8fdb25357e596ba08f323df27.js

711 ms

effect.min.js

effect.min.js

707 ms

autoptimize_single_817a3ac32e051730da522b22c1a449e6.js

autoptimize_single_817a3ac32e051730da522b22c1a449e6.js

701 ms

autoptimize_single_f9d38fae132cd66ecefe89a509ec54a1.js

autoptimize_single_f9d38fae132cd66ecefe89a509ec54a1.js

692 ms

autoptimize_single_d1c3432f25d3a5defba2b3bf5ba15ece.js

autoptimize_single_d1c3432f25d3a5defba2b3bf5ba15ece.js

678 ms

autoptimize_single_8c6a778e3cc708f63a43286f54fde2e7.js

autoptimize_single_8c6a778e3cc708f63a43286f54fde2e7.js

619 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

630 ms

underscore.min.js

underscore.min.js

625 ms

wp-util.min.js

wp-util.min.js

622 ms

backbone.min.js

backbone.min.js

564 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

653 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

592 ms

wp-playlist.min.js

wp-playlist.min.js

588 ms

webpack.runtime.min.js

webpack.runtime.min.js

538 ms

frontend-modules.min.js

frontend-modules.min.js

539 ms

waypoints.min.js

waypoints.min.js

557 ms

core.min.js

core.min.js

561 ms

frontend.min.js

frontend.min.js

544 ms

open-paas.org

open-paas.org

1438 ms

Catamaran-Regular.ttf

Catamaran-Regular.ttf

401 ms

fa-solid-900.woff

fa-solid-900.woff

403 ms

fa-regular-400.woff

fa-regular-400.woff

402 ms

owa.tracker-combined-min.js

owa.tracker-combined-min.js

647 ms

fa-brands-400.woff

fa-brands-400.woff

405 ms

Catamaran-SemiBold.ttf

Catamaran-SemiBold.ttf

469 ms

matomo.js

matomo.js

757 ms

MaterialIcons-Regular.woff

MaterialIcons-Regular.woff

344 ms

openpaas-2.png

openpaas-2.png

318 ms

openpaas-product-image-768x330-1.png

openpaas-product-image-768x330-1.png

427 ms

wheelchair.png

wheelchair.png

382 ms

aimail.png

aimail.png

92 ms

securefile.png

securefile.png

91 ms

video.png

video.png

89 ms

log.php

log.php

333 ms

matomo.php

matomo.php

334 ms

autoptimize_single_9afbeb5612eb7edc770fa602bdf6ca2c.css

autoptimize_single_9afbeb5612eb7edc770fa602bdf6ca2c.css

94 ms

Accessibility Review

open-paas.org accessibility score

91

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

open-paas.org 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

open-paas.org SEO score

90

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

    FR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Open-paas.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed French language. Our system also found out that Open-paas.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-paas.org

Open Graph data is detected on the main page of Open Paas. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: