Report Summary

  • 53

    Performance

    Renders faster than
    71% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 46% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

api-web.be

Api Web - Création de sites internet, création graphique

Page Load Speed

4.7 sec in total

First Response

1.6 sec

Resources Loaded

2.9 sec

Page Rendered

205 ms

api-web.be screenshot

About Website

Welcome to api-web.be homepage info - get ready to check Api Web best content right away, or after learning these important things about api-web.be

Api Web, programmation et mise en ligne ne font plus qu'un ! Confiez-nous vos projets internet quels qu'ils soient et nous les mènerons à bien

Visit api-web.be

Key Findings

We analyzed Api-web.be page load time and found that the first response time was 1.6 sec and then it took 3.1 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

api-web.be performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

84/100

10%

LCP (Largest Contentful Paint)

Value7.6 s

3/100

25%

SI (Speed Index)

Value3.6 s

86/100

10%

TBT (Total Blocking Time)

Value610 ms

49/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value6.5 s

58/100

10%

Network Requests Diagram

api-web.be

1591 ms

bootstrap.css

381 ms

docs.css

740 ms

prettify.css

227 ms

tm_docs.css

347 ms

Our browser made a total of 18 requests to load all elements on the main page. We found that 83% of them (15 requests) were addressed to the original Api-web.be, 11% (2 requests) were made to Apis.google.com and 6% (1 request) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Api-web.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 323.2 kB (69%)

Content Size

469.7 kB

After Optimization

146.5 kB

In fact, the total size of Api-web.be main page is 469.7 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. 25% of websites need less resources to load. CSS take 241.4 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 7.2 kB

  • Original 9.1 kB
  • After minification 7.1 kB
  • After compression 2.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 2.0 kB, which is 22% 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 7.2 kB or 79% of the original size.

Image Optimization

-14%

Potential reduce by 3.6 kB

  • Original 26.0 kB
  • After minification 22.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. Obviously, Api Web needs image optimization as it can save up to 3.6 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-71%

Potential reduce by 137.1 kB

  • Original 193.2 kB
  • After minification 165.6 kB
  • After compression 56.2 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 137.1 kB or 71% of the original size.

CSS Optimization

-73%

Potential reduce by 175.3 kB

  • Original 241.4 kB
  • After minification 204.0 kB
  • After compression 66.0 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-web.be needs all CSS files to be minified and compressed as it can save up to 175.3 kB or 73% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (81%)

Requests Now

16

After Optimization

3

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

Accessibility Review

api-web.be accessibility score

78

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

Image elements do not have [alt] attributes

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

api-web.be 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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

api-web.be SEO score

86

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    FR

  • Language Claimed

    EN

  • Encoding

    UTF-8

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