Tools & Wizards About Us
openswoole.com screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 95

    SEO

    Google-friendlier than
    90% of websites

openswoole.com

Open Swoole: PHP Server with Async IO, Coroutines and Fibers (previously Swoole) | Open Swoole PHP

Page Load Speed

1.5 sec in total

First Response

227 ms

Resources Loaded

767 ms

Page Rendered

462 ms

openswoole.com screenshot

About Website

Visit openswoole.com now to see the best up-to-date Open Swoole content for Indonesia and also check out these interesting facts you probably never knew about openswoole.com

Use Open Swoole to build high-performance, scalable, concurrent TCP, UDP, Unix Socket, HTTP, WebSocket services with PHP without too much knowledge about non-blocking I/O programming and low-level Lin...

Visit openswoole.com

Key Findings

We analyzed Openswoole.com page load time and found that the first response time was 227 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

openswoole.com performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

24/100

25%

SI (Speed Index)

Value6.0 s

46/100

10%

TBT (Total Blocking Time)

Value1,300 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value9.9 s

27/100

10%

Network Requests Diagram

openswoole.com

227 ms

b5a635e307.js

151 ms

stub.min.js

50 ms

cmp.js

420 ms

tag.js

168 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 60% of them (15 requests) were addressed to the original Openswoole.com, 8% (2 requests) were made to Cmp.uniconsent.com and 4% (1 request) were made to T.pubperf.com. The less responsive or slowest element that took the longest time to load (420 ms) relates to the external source Cmp.uniconsent.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 253.7 kB (40%)

Content Size

632.4 kB

After Optimization

378.8 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Openswoole.com main page is 632.4 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. 30% of websites need less resources to load. Images take 333.7 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 131.1 kB

  • Original 146.5 kB
  • After minification 146.5 kB
  • After compression 15.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. 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 131.1 kB or 89% of the original size.

Image Optimization

-35%

Potential reduce by 117.0 kB

  • Original 333.7 kB
  • After minification 216.6 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. Obviously, Open Swoole needs image optimization as it can save up to 117.0 kB or 35% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-4%

Potential reduce by 5.6 kB

  • Original 152.3 kB
  • After minification 152.3 kB
  • After compression 146.7 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 13 (57%)

Requests Now

23

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

openswoole.com

openswoole.com

227 ms

b5a635e307.js

b5a635e307.js

151 ms

stub.min.js

stub.min.js

50 ms

cmp.js

cmp.js

420 ms

tag.js

tag.js

168 ms

tag.js

tag.js

66 ms

1f06617b89690def.css

1f06617b89690def.css

42 ms

b47b1203cb48a5ab.css

b47b1203cb48a5ab.css

77 ms

bundle.3e9df1ab.css

bundle.3e9df1ab.css

36 ms

email-decode.min.js

email-decode.min.js

28 ms

vendor.js

vendor.js

104 ms

bundle.3e9df1ab.js

bundle.3e9df1ab.js

85 ms

openswoole.6c091292.js

openswoole.6c091292.js

86 ms

js

js

115 ms

5.1.0

5.1.0

50 ms

beacon.min.js

beacon.min.js

83 ms

css

css

24 ms

swoole-logo.svg

swoole-logo.svg

152 ms

openswoole-grpc-connection-pool.png

openswoole-grpc-connection-pool.png

50 ms

openswoole-v22.0.png

openswoole-v22.0.png

120 ms

openswoole-v4120.png

openswoole-v4120.png

119 ms

openswoole-grpc.png

openswoole-grpc.png

119 ms

openswoole-calver-semver.png

openswoole-calver-semver.png

210 ms

openswoole-v4111.png

openswoole-v4111.png

78 ms

font

font

82 ms

Accessibility Review

openswoole.com accessibility score

80

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

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

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

Missing source maps for large first-party JavaScript

SEO Factors

openswoole.com SEO score

95

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

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

openswoole.com

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