Report Summary

  • 40

    Performance

    Renders faster than
    59% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

clacklisp.org

GitHub - fukamachi/clack: Web server abstraction layer for Common Lisp

Page Load Speed

5.3 sec in total

First Response

586 ms

Resources Loaded

4.5 sec

Page Rendered

234 ms

About Website

Click here to check amazing Clack Lisp content. Otherwise, check out these important facts you probably never knew about clacklisp.org

Web server abstraction layer for Common Lisp. Contribute to fukamachi/clack development by creating an account on GitHub.

Visit clacklisp.org

Key Findings

We analyzed Clacklisp.org page load time and found that the first response time was 586 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

clacklisp.org performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

36/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

55/100

25%

SI (Speed Index)

Value5.7 s

52/100

10%

TBT (Total Blocking Time)

Value3,130 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.5 s

18/100

10%

Network Requests Diagram

clacklisp.org

586 ms

clack

399 ms

light-fec97922b76c.css

66 ms

dark-e8b003732d38.css

72 ms

primer-primitives-ebd37ecbf27d.css

73 ms

Our browser made a total of 103 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Clacklisp.org, 82% (84 requests) were made to Github.githubassets.com and 14% (14 requests) were made to Avatars.githubusercontent.com. The less responsive or slowest element that took the longest time to load (3.5 sec) relates to the external source Camo.githubusercontent.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 376.5 kB (27%)

Content Size

1.4 MB

After Optimization

1.0 MB

In fact, the total size of Clacklisp.org main page is 1.4 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. 75% 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. Javascripts take 856.8 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 313.1 kB

  • Original 366.9 kB
  • After minification 357.6 kB
  • After compression 53.8 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 313.1 kB or 85% of the original size.

Image Optimization

-14%

Potential reduce by 5.4 kB

  • Original 38.1 kB
  • After minification 32.7 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, Clack Lisp needs image optimization as it can save up to 5.4 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

-6%

Potential reduce by 52.2 kB

  • Original 856.8 kB
  • After minification 856.8 kB
  • After compression 804.7 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. This website has mostly compressed JavaScripts.

CSS Optimization

-4%

Potential reduce by 5.8 kB

  • Original 138.8 kB
  • After minification 138.8 kB
  • After compression 133.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. Clacklisp.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 82 (82%)

Requests Now

100

After Optimization

18

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

Accessibility Review

clacklisp.org accessibility score

92

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

clacklisp.org best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

clacklisp.org SEO score

91

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

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 Clacklisp.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 Clacklisp.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 data is detected on the main page of Clack Lisp. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: