Report Summary

  • 40

    Performance

    Renders faster than
    59% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

perldancer.org

Dancer - Perl Web Framework for easy and fun webapp development

Page Load Speed

1.6 sec in total

First Response

403 ms

Resources Loaded

951 ms

Page Rendered

246 ms

About Website

Visit perldancer.org now to see the best up-to-date Perl Dancer content for Indonesia and also check out these interesting facts you probably never knew about perldancer.org

PerlDancer is a micro perl web framework designed to be as effortless as possible for the developer. With PerlDancer, web development is fun again. It's a very expressive DSL for writing web applicati...

Visit perldancer.org

Key Findings

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

Performance Metrics

perldancer.org performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value7.6 s

4/100

25%

SI (Speed Index)

Value5.3 s

58/100

10%

TBT (Total Blocking Time)

Value940 ms

30/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.1 s

52/100

10%

Network Requests Diagram

perldancer.org

403 ms

style.css

77 ms

tweets.css

153 ms

prettify.css

155 ms

prettify.js

158 ms

Our browser made a total of 24 requests to load all elements on the main page. We found that 75% of them (18 requests) were addressed to the original Perldancer.org, 13% (3 requests) were made to Ajax.googleapis.com and 8% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (403 ms) belongs to the original domain Perldancer.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 94.2 kB (26%)

Content Size

356.8 kB

After Optimization

262.6 kB

In fact, the total size of Perldancer.org main page is 356.8 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. Images take 301.1 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 18.5 kB

  • Original 26.0 kB
  • After minification 22.4 kB
  • After compression 7.5 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 3.6 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 18.5 kB or 71% of the original size.

Image Optimization

-23%

Potential reduce by 68.4 kB

  • Original 301.1 kB
  • After minification 232.6 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, Perl Dancer needs image optimization as it can save up to 68.4 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-25%

Potential reduce by 7.3 kB

  • Original 29.8 kB
  • After minification 29.6 kB
  • After compression 22.5 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 7.3 kB or 25% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (22%)

Requests Now

23

After Optimization

18

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

Accessibility Review

perldancer.org accessibility score

94

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

Links do not have a discernible name

Best Practices

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

SEO Factors

perldancer.org SEO score

67

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 Perldancer.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 Perldancer.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 Perl Dancer. 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: