Report Summary

  • 81

    Performance

    Renders faster than
    87% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

px4.io

Open Source Autopilot for Drones - PX4 Autopilot

Page Load Speed

3.5 sec in total

First Response

151 ms

Resources Loaded

2.2 sec

Page Rendered

1.1 sec

px4.io screenshot

About Website

Visit px4.io now to see the best up-to-date PX4 content for China and also check out these interesting facts you probably never knew about px4.io

Professional open source autopilot solution.

Visit px4.io

Key Findings

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

Performance Metrics

px4.io performance score

81

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

67/100

10%

LCP (Largest Contentful Paint)

Value2.8 s

82/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value210 ms

88/100

30%

CLS (Cumulative Layout Shift)

Value0.136

80/100

15%

TTI (Time to Interactive)

Value6.7 s

56/100

10%

Network Requests Diagram

px4.io

151 ms

sidecar.v1.js

170 ms

analytics.js

72 ms

wp-emoji-release.min.js

69 ms

bean-shortcodes.min.css

69 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 56% of them (48 requests) were addressed to the original Px4.io, 10% (9 requests) were made to I.ytimg.com and 8% (7 requests) were made to Px4.flywheelsites.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Px4.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (29%)

Content Size

4.2 MB

After Optimization

3.0 MB

In fact, the total size of Px4.io main page is 4.2 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.9 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 55.6 kB

  • Original 70.7 kB
  • After minification 65.5 kB
  • After compression 15.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 55.6 kB or 79% of the original size.

Image Optimization

-10%

Potential reduce by 306.0 kB

  • Original 2.9 MB
  • After minification 2.6 MB

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. PX4 images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 480.5 kB

  • Original 731.3 kB
  • After minification 726.8 kB
  • After compression 250.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 480.5 kB or 66% of the original size.

CSS Optimization

-83%

Potential reduce by 356.6 kB

  • Original 428.4 kB
  • After minification 392.0 kB
  • After compression 71.8 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. Px4.io needs all CSS files to be minified and compressed as it can save up to 356.6 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (47%)

Requests Now

72

After Optimization

38

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

Accessibility Review

px4.io accessibility score

82

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

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

px4.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

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

SEO Factors

px4.io SEO score

86

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

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

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