Tools & Wizards About Us
haskell.org screenshot

Report Summary

  • 65

    Performance

    Renders faster than
    78% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 96

    SEO

    Google-friendlier than
    90% of websites

haskell.org

Haskell Language

Page Load Speed

1.6 sec in total

First Response

100 ms

Resources Loaded

879 ms

Page Rendered

632 ms

haskell.org screenshot

About Website

Visit haskell.org now to see the best up-to-date Haskell content for Brazil and also check out these interesting facts you probably never knew about haskell.org

The Haskell purely functional programming language home page.

Visit haskell.org

Key Findings

We analyzed Haskell.org page load time and found that the first response time was 100 ms and then it took 1.5 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

haskell.org performance score

65

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value3.5 s

88/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.094

91/100

15%

TTI (Time to Interactive)

Value5.1 s

75/100

10%

Network Requests Diagram

haskell.org

100 ms

haskell.org

146 ms

www.haskell.org

212 ms

fonts.css

61 ms

hl.css

124 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 78% of them (31 requests) were addressed to the original Haskell.org, 15% (6 requests) were made to I1.ytimg.com and 5% (2 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (299 ms) relates to the external source Static.scarf.sh.

Page Optimization Overview & Recommendations

Page size can be reduced by 395.4 kB (38%)

Content Size

1.0 MB

After Optimization

645.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-83%

Potential reduce by 51.9 kB

  • Original 62.3 kB
  • After minification 49.2 kB
  • After compression 10.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. This page needs HTML code to be minified as it can gain 13.1 kB, which is 21% 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 51.9 kB or 83% of the original size.

Image Optimization

-18%

Potential reduce by 120.9 kB

  • Original 685.7 kB
  • After minification 564.9 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, Haskell needs image optimization as it can save up to 120.9 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-72%

Potential reduce by 140.1 kB

  • Original 193.2 kB
  • After minification 163.4 kB
  • After compression 53.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 140.1 kB or 72% of the original size.

CSS Optimization

-83%

Potential reduce by 82.6 kB

  • Original 99.7 kB
  • After minification 99.5 kB
  • After compression 17.2 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. Haskell.org needs all CSS files to be minified and compressed as it can save up to 82.6 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (16%)

Requests Now

37

After Optimization

31

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

haskell.org

haskell.org

100 ms

haskell.org

haskell.org

146 ms

www.haskell.org

www.haskell.org

212 ms

fonts.css

fonts.css

61 ms

hl.css

hl.css

124 ms

glider.min.css

glider.min.css

16 ms

glider.min.js

glider.min.js

18 ms

jquery.js

jquery.js

135 ms

bootstrap.min.js

bootstrap.min.js

132 ms

home.js

home.js

130 ms

jquery.console.js

jquery.console.js

135 ms

tryhaskell.js

tryhaskell.js

129 ms

tryhaskell.pages.js

tryhaskell.pages.js

158 ms

mqdefault.jpg

mqdefault.jpg

130 ms

a.png

a.png

299 ms

haskell-logo.svg

haskell-logo.svg

113 ms

haskell-uwu.png

haskell-uwu.png

169 ms

pattern.png

pattern.png

265 ms

bellroy.png

bellroy.png

114 ms

bitnomial.png

bitnomial.png

115 ms

calabrio.png

calabrio.png

115 ms

centralapp.png

centralapp.png

144 ms

e-bot7.png

e-bot7.png

145 ms

finn.png

finn.png

143 ms

fission.png

fission.png

144 ms

foxhoundsystems.png

foxhoundsystems.png

173 ms

hasura.png

hasura.png

174 ms

imagineai.png

imagineai.png

174 ms

iohk.png

iohk.png

175 ms

mercury.png

mercury.png

197 ms

noredink.png

noredink.png

203 ms

scarf.png

scarf.png

204 ms

serokell.png

serokell.png

204 ms

stackbuilders.png

stackbuilders.png

206 ms

EM-Horizontal-White.svg

EM-Horizontal-White.svg

226 ms

mqdefault.jpg

mqdefault.jpg

115 ms

mqdefault.jpg

mqdefault.jpg

124 ms

mqdefault.jpg

mqdefault.jpg

121 ms

mqdefault.jpg

mqdefault.jpg

122 ms

mqdefault.jpg

mqdefault.jpg

120 ms

Accessibility Review

haskell.org accessibility score

82

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

High

Form elements do not have associated labels

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

haskell.org best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

haskell.org SEO score

96

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

haskell.org

Open Graph description is not detected on the main page of Haskell. 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: