Tools & Wizards About Us

Report Summary

  • 86

    Performance

    Renders faster than
    89% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

funix.org

FUNIX

Page Load Speed

1.7 sec in total

First Response

264 ms

Resources Loaded

1.2 sec

Page Rendered

179 ms

About Website

Click here to check amazing FUNIX content for Morocco. Otherwise, check out these important facts you probably never knew about funix.org

Site consacré à Linux et aux logiciels libres

Visit funix.org

Key Findings

We analyzed Funix.org page load time and found that the first response time was 264 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

funix.org performance score

86

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

85/100

10%

LCP (Largest Contentful Paint)

Value4.0 s

50/100

25%

SI (Speed Index)

Value2.8 s

96/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.031

100/100

15%

TTI (Time to Interactive)

Value2.0 s

99/100

10%

Network Requests Diagram

funix.org

264 ms

www.funix.org

442 ms

style.css

80 ms

btn_donate_LG.gif

18 ms

88x31.png

68 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that 78% of them (18 requests) were addressed to the original Funix.org, 9% (2 requests) were made to Paypalobjects.com and 4% (1 request) were made to I.creativecommons.org. The less responsive or slowest element that took the longest time to load (541 ms) relates to the external source Rss.bloople.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 11.9 kB (18%)

Content Size

67.2 kB

After Optimization

55.3 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Funix.org main page is 67.2 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. Only 10% of websites need less resources to load. Images take 51.3 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 10.3 kB

  • Original 14.6 kB
  • After minification 12.5 kB
  • After compression 4.3 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.1 kB, which is 14% 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 10.3 kB or 70% of the original size.

Image Optimization

-2%

Potential reduce by 1.2 kB

  • Original 51.3 kB
  • After minification 50.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. FUNIX images are well optimized though.

CSS Optimization

-32%

Potential reduce by 406 B

  • Original 1.3 kB
  • After minification 1.3 kB
  • After compression 876 B

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. Funix.org needs all CSS files to be minified and compressed as it can save up to 406 B or 32% of the original size.

Requests Breakdown

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

Requests Now

20

After Optimization

13

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

funix.org accessibility score

61

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Form elements do not have associated labels

Best Practices

funix.org best practices score

67

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

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

funix.org SEO score

62

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

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    FR

  • Encoding

    UTF-8

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