Report Summary

  • 68

    Performance

    Renders faster than
    81% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

screem.org

Screem HTML/XML Editor - About

Page Load Speed

836 ms in total

First Response

215 ms

Resources Loaded

477 ms

Page Rendered

144 ms

screem.org screenshot

About Website

Click here to check amazing Screem content. Otherwise, check out these important facts you probably never knew about screem.org

SCREEM is an open source HTML/XML editor for unix based systems, and the GNOME desktop environment

Visit screem.org

Key Findings

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

Performance Metrics

screem.org performance score

68

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

38/100

25%

SI (Speed Index)

Value6.4 s

40/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.082

94/100

15%

TTI (Time to Interactive)

Value4.4 s

83/100

10%

Network Requests Diagram

screem.org

215 ms

main.css

41 ms

init.js

59 ms

non-nn4.css

30 ms

sflogo.php

57 ms

Our browser made a total of 12 requests to load all elements on the main page. We found that 92% of them (11 requests) were addressed to the original Screem.org, 8% (1 request) were made to Sourceforge.net. The less responsive or slowest element that took the longest time to load (215 ms) belongs to the original domain Screem.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 10.9 kB (23%)

Content Size

47.7 kB

After Optimization

36.8 kB

In fact, the total size of Screem.org main page is 47.7 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. Images take 37.3 kB which makes up the majority of the site volume.

HTML Optimization

-62%

Potential reduce by 3.3 kB

  • Original 5.4 kB
  • After minification 5.2 kB
  • After compression 2.1 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 3.3 kB or 62% of the original size.

Image Optimization

-11%

Potential reduce by 3.9 kB

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

JavaScript Optimization

-65%

Potential reduce by 704 B

  • Original 1.1 kB
  • After minification 709 B
  • After compression 386 B

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 704 B or 65% of the original size.

CSS Optimization

-74%

Potential reduce by 2.9 kB

  • Original 4.0 kB
  • After minification 3.0 kB
  • After compression 1.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. Screem.org needs all CSS files to be minified and compressed as it can save up to 2.9 kB or 74% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

11

After Optimization

11

The browser has sent 11 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Screem. According to our analytics all requests are already optimized.

Accessibility Review

screem.org accessibility score

83

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best Practices

screem.org 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

Serves images with low resolution

SEO Factors

screem.org SEO score

75

Search Engine Optimization Advices

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 Screem.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 Screem.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 Screem. 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: