Tools & Wizards About Us
weje.io screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

weje.io

Weje.io — all-in-one online team collaboration tool

Page Load Speed

4.3 sec in total

First Response

353 ms

Resources Loaded

3.6 sec

Page Rendered

385 ms

weje.io screenshot

About Website

Welcome to weje.io homepage info - get ready to check Weje best content for Philippines right away, or after learning these important things about weje.io

Visualize your ideas on Weje's canvas, group and share ideas and brainstorms on this collaboration software platform, communicate with your team live

Visit weje.io

Key Findings

We analyzed Weje.io page load time and found that the first response time was 353 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

weje.io performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value16.0 s

0/100

25%

SI (Speed Index)

Value15.9 s

0/100

10%

TBT (Total Blocking Time)

Value8,000 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.021

100/100

15%

TTI (Time to Interactive)

Value29.8 s

0/100

10%

Network Requests Diagram

weje.io

353 ms

app.css

178 ms

marketing.js

240 ms

appStyle.css

352 ms

style.css

256 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that 46% of them (41 requests) were addressed to the original Weje.io, 14% (13 requests) were made to Fonts.gstatic.com and 10% (9 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Weje.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 117.1 kB (11%)

Content Size

1.1 MB

After Optimization

951.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Weje.io main page is 1.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. Only a small number of websites need less resources to load. Images take 439.7 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 32.4 kB

  • Original 39.8 kB
  • After minification 32.0 kB
  • After compression 7.4 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.8 kB, which is 20% 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 32.4 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 3.6 kB

  • Original 439.7 kB
  • After minification 436.1 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. Weje images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 55.2 kB

  • Original 366.3 kB
  • After minification 364.7 kB
  • After compression 311.1 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 55.2 kB or 15% of the original size.

CSS Optimization

-12%

Potential reduce by 25.8 kB

  • Original 222.9 kB
  • After minification 222.9 kB
  • After compression 197.1 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. Weje.io needs all CSS files to be minified and compressed as it can save up to 25.8 kB or 12% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (60%)

Requests Now

67

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

weje.io

weje.io

353 ms

app.css

app.css

178 ms

marketing.js

marketing.js

240 ms

appStyle.css

appStyle.css

352 ms

style.css

style.css

256 ms

optimize.js

optimize.js

86 ms

owl.carousel.min.css

owl.carousel.min.css

258 ms

jquery.fancybox.min.css

jquery.fancybox.min.css

260 ms

main.css

main.css

271 ms

wpforms-full.min.css

wpforms-full.min.css

401 ms

js_composer.min.css

js_composer.min.css

576 ms

css2

css2

63 ms

jquery-3.6.0.min.js

jquery-3.6.0.min.js

56 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

53 ms

gsap.min.js

gsap.min.js

75 ms

ScrollTrigger.min.js

ScrollTrigger.min.js

84 ms

appAnimation.js

appAnimation.js

402 ms

appScript.js

appScript.js

404 ms

owl.carousel.css

owl.carousel.css

451 ms

owl.theme.default.css

owl.theme.default.css

521 ms

owl.carousel.min.js

owl.carousel.min.js

86 ms

jquery.js

jquery.js

633 ms

owl.carousel.min.js

owl.carousel.min.js

520 ms

jquery.fancybox.min.js

jquery.fancybox.min.js

606 ms

main.js

main.js

607 ms

js_composer_front.min.js

js_composer_front.min.js

606 ms

vc-accordion.min.js

vc-accordion.min.js

613 ms

vc-tta-autoplay.min.js

vc-tta-autoplay.min.js

736 ms

gtm.js

gtm.js

64 ms

js

js

72 ms

analytics.js

analytics.js

106 ms

normalize.min.css

normalize.min.css

351 ms

top-post-badge.svg

top-post-badge.svg

156 ms

SebDEpOwO08

SebDEpOwO08

214 ms

r42PzT_im6Y

r42PzT_im6Y

468 ms

oWm7_BOoKdM

oWm7_BOoKdM

406 ms

UMiR7ej1xbM

UMiR7ej1xbM

421 ms

tEnzwjHyoZk

tEnzwjHyoZk

443 ms

logo.svg

logo.svg

341 ms

template-thumb-1.jpg

template-thumb-1.jpg

1006 ms

template-thumb-2.jpg

template-thumb-2.jpg

1045 ms

template-thumb-3.jpg

template-thumb-3.jpg

1005 ms

medal-g21-147x191.png

medal-g21-147x191.png

1004 ms

footer-logo.svg

footer-logo.svg

1002 ms

google-play.png

google-play.png

1003 ms

top-post-badge.svg

top-post-badge.svg

204 ms

top-post-badge.svg

top-post-badge.svg

320 ms

collect

collect

28 ms

collect

collect

92 ms

special-style.css

special-style.css

884 ms

pxiEyp8kv8JHgFVrFJA.ttf

pxiEyp8kv8JHgFVrFJA.ttf

98 ms

pxiByp8kv8JHgFVrLGT9V1s.ttf

pxiByp8kv8JHgFVrLGT9V1s.ttf

192 ms

pxiByp8kv8JHgFVrLDz8V1s.ttf

pxiByp8kv8JHgFVrLDz8V1s.ttf

285 ms

pxiByp8kv8JHgFVrLFj_V1s.ttf

pxiByp8kv8JHgFVrLFj_V1s.ttf

308 ms

pxiGyp8kv8JHgFVrLPTedw.ttf

pxiGyp8kv8JHgFVrLPTedw.ttf

307 ms

pxiByp8kv8JHgFVrLEj6V1s.ttf

pxiByp8kv8JHgFVrLEj6V1s.ttf

308 ms

pxiByp8kv8JHgFVrLCz7V1s.ttf

pxiByp8kv8JHgFVrLCz7V1s.ttf

307 ms

pxiByp8kv8JHgFVrLDD4V1s.ttf

pxiByp8kv8JHgFVrLDD4V1s.ttf

307 ms

pxiByp8kv8JHgFVrLBT5V1s.ttf

pxiByp8kv8JHgFVrLBT5V1s.ttf

310 ms

js

js

88 ms

loader.js

loader.js

283 ms

hotjar-2347620.js

hotjar-2347620.js

282 ms

www-player.css

www-player.css

112 ms

www-embed-player.js

www-embed-player.js

144 ms

base.js

base.js

258 ms

modules.a4fd7e5489291affcf56.js

modules.a4fd7e5489291affcf56.js

510 ms

ad_status.js

ad_status.js

500 ms

menu-arrow.svg

menu-arrow.svg

446 ms

more.svg

more.svg

447 ms

6mt_jkCC8QEMfVv4UaXe0WVRezbgElH9_VSMBGBwk28.js

6mt_jkCC8QEMfVv4UaXe0WVRezbgElH9_VSMBGBwk28.js

449 ms

embed.js

embed.js

219 ms

id

id

160 ms

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A99d.ttf

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A99d.ttf

35 ms

NotoSans-Regular.woff

NotoSans-Regular.woff

937 ms

NotoSans-Medium.woff

NotoSans-Medium.woff

936 ms

NotoSans-Light.woff

NotoSans-Light.woff

662 ms

NotoSans-ExtraLight.woff

NotoSans-ExtraLight.woff

937 ms

NotoSans-Thin.woff

NotoSans-Thin.woff

662 ms

NotoSans-SemiBold.woff

NotoSans-SemiBold.woff

659 ms

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyAaBN9d.ttf

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyAaBN9d.ttf

32 ms

NotoSans-Bold.woff

NotoSans-Bold.woff

934 ms

NotoSans-ExtraBold.woff

NotoSans-ExtraBold.woff

931 ms

NotoSans-Black.woff

NotoSans-Black.woff

935 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

25 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

24 ms

Create

Create

639 ms

Create

Create

643 ms

Create

Create

645 ms

Create

Create

647 ms

Create

Create

906 ms

Accessibility Review

weje.io accessibility score

66

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

Links do not have a discernible name

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

weje.io best practices score

75

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

weje.io SEO score

100

Search Engine Optimization Advices

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

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

weje.io

Open Graph description is not detected on the main page of Weje. 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: