Report Summary

  • 88

    Performance

    Renders faster than
    90% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 58

    SEO

    Google-friendlier than
    20% of websites

api.openfl.org

openfl - API Reference

Page Load Speed

791 ms in total

First Response

174 ms

Resources Loaded

496 ms

Page Rendered

121 ms

api.openfl.org screenshot

About Website

Visit api.openfl.org now to see the best up-to-date API Openfl content for Morocco and also check out these interesting facts you probably never knew about api.openfl.org

Visit api.openfl.org

Key Findings

We analyzed Api.openfl.org page load time and found that the first response time was 174 ms and then it took 617 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

api.openfl.org performance score

88

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

70/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

67/100

25%

SI (Speed Index)

Value2.4 s

98/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.066

97/100

15%

TTI (Time to Interactive)

Value3.3 s

94/100

10%

Network Requests Diagram

api.openfl.org

174 ms

bootstrap.min.css

87 ms

bootstrap-responsive.min.css

120 ms

jquery-1.9.1.min.js

170 ms

bootstrap.min.js

124 ms

Our browser made a total of 13 requests to load all elements on the main page. We found that 85% of them (11 requests) were addressed to the original Api.openfl.org, 15% (2 requests) were made to Google-code-prettify.googlecode.com. The less responsive or slowest element that took the longest time to load (174 ms) belongs to the original domain Api.openfl.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 721.3 kB (86%)

Content Size

842.5 kB

After Optimization

121.2 kB

In fact, the total size of Api.openfl.org main page is 842.5 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. Javascripts take 403.6 kB which makes up the majority of the site volume.

HTML Optimization

-93%

Potential reduce by 274.4 kB

  • Original 295.4 kB
  • After minification 257.7 kB
  • After compression 21.0 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 37.7 kB, which is 13% 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 274.4 kB or 93% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 16.4 kB
  • After minification 16.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. API Openfl images are well optimized though.

JavaScript Optimization

-85%

Potential reduce by 341.6 kB

  • Original 403.6 kB
  • After minification 403.0 kB
  • After compression 62.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 341.6 kB or 85% of the original size.

CSS Optimization

-83%

Potential reduce by 105.3 kB

  • Original 127.1 kB
  • After minification 125.0 kB
  • After compression 21.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. Api.openfl.org needs all CSS files to be minified and compressed as it can save up to 105.3 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (64%)

Requests Now

11

After Optimization

4

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

Accessibility Review

api.openfl.org accessibility score

92

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

Links do not have a discernible name

Best Practices

api.openfl.org best practices score

75

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

Page has valid source maps

SEO Factors

api.openfl.org SEO score

58

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Api.openfl.org 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 Api.openfl.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 Graph description is not detected on the main page of API Openfl. 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: