Tools & Wizards About Us
gutenbergnews.org screenshot

Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

gutenbergnews.org

Gutenberg News | Home

Page Load Speed

3.5 sec in total

First Response

114 ms

Resources Loaded

2.1 sec

Page Rendered

1.3 sec

gutenbergnews.org screenshot

About Website

Welcome to gutenbergnews.org homepage info - get ready to check Gutenberg News best content for United States right away, or after learning these important things about gutenbergnews.org

News on the latest ebook releases from Project Gutenberg and other information about digital publishing.

Visit gutenbergnews.org

Key Findings

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

Performance Metrics

gutenbergnews.org performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value3.6 s

62/100

25%

SI (Speed Index)

Value6.2 s

44/100

10%

TBT (Total Blocking Time)

Value2,700 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.012

100/100

15%

TTI (Time to Interactive)

Value13.8 s

10/100

10%

Network Requests Diagram

gutenbergnews.org

114 ms

www.gutenbergnews.org

384 ms

layout.css

72 ms

custom.css

70 ms

widget.css

68 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 31% of them (25 requests) were addressed to the original Gutenbergnews.org, 10% (8 requests) were made to Apis.google.com and 8% (6 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (922 ms) relates to the external source Connect.facebook.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 376.8 kB (54%)

Content Size

703.9 kB

After Optimization

327.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gutenbergnews.org main page is 703.9 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. 60% of websites need less resources to load. Javascripts take 399.1 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 60.0 kB

  • Original 84.2 kB
  • After minification 83.6 kB
  • After compression 24.2 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 60.0 kB or 71% of the original size.

Image Optimization

-1%

Potential reduce by 1.8 kB

  • Original 166.3 kB
  • After minification 164.5 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. Gutenberg News images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 270.3 kB

  • Original 399.1 kB
  • After minification 392.2 kB
  • After compression 128.8 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 270.3 kB or 68% of the original size.

CSS Optimization

-82%

Potential reduce by 44.6 kB

  • Original 54.4 kB
  • After minification 41.2 kB
  • After compression 9.8 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. Gutenbergnews.org needs all CSS files to be minified and compressed as it can save up to 44.6 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (61%)

Requests Now

71

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gutenbergnews.org

gutenbergnews.org

114 ms

www.gutenbergnews.org

www.gutenbergnews.org

384 ms

layout.css

layout.css

72 ms

custom.css

custom.css

70 ms

widget.css

widget.css

68 ms

wpcf.css

wpcf.css

70 ms

twitter-feed.css

twitter-feed.css

95 ms

frontend.css

frontend.css

147 ms

style.css

style.css

148 ms

base.css

base.css

148 ms

widgets.js

widgets.js

120 ms

hostedbadge.php

hostedbadge.php

338 ms

adsbygoogle.js

adsbygoogle.js

8 ms

show_ads.js

show_ads.js

10 ms

wp-embed.min.js

wp-embed.min.js

139 ms

analytics.js

analytics.js

22 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

81 ms

collect

collect

24 ms

dot-ddd.gif

dot-ddd.gif

39 ms

image-3132383-10386157

image-3132383-10386157

24 ms

all.js

all.js

922 ms

plusone.js

plusone.js

70 ms

bg-header-top.jpg

bg-header-top.jpg

122 ms

top-stain.gif

top-stain.gif

122 ms

bg-header-bottom.jpg

bg-header-bottom.jpg

121 ms

cat-sep.gif

cat-sep.gif

94 ms

line.png

line.png

95 ms

bg-cat.gif

bg-cat.gif

96 ms

bg-link.gif

bg-link.gif

143 ms

bg-search.png

bg-search.png

238 ms

bg-trans.png

bg-trans.png

176 ms

collect

collect

91 ms

10386157-1439463822794

10386157-1439463822794

28 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

13 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

35 ms

fastbutton

fastbutton

74 ms

ga-audiences

ga-audiences

84 ms

postmessageRelay

postmessageRelay

65 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

32 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

21 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

659 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

733 ms

rpc:shindig_random.js

rpc:shindig_random.js

635 ms

widgets.js

widgets.js

644 ms

ca-pub-1772498673108330.js

ca-pub-1772498673108330.js

718 ms

zrt_lookup.html

zrt_lookup.html

714 ms

show_ads_impl.js

show_ads_impl.js

643 ms

bg-footer-top.jpg

bg-footer-top.jpg

668 ms

bg-footer-fill.jpg

bg-footer-fill.jpg

694 ms

bg-footerstain.jpg

bg-footerstain.jpg

710 ms

widgets.js

widgets.js

725 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

161 ms

163 ms

ads

ads

205 ms

osd.js

osd.js

26 ms

63 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

21 ms

ads

ads

184 ms

xd_arbiter.php

xd_arbiter.php

219 ms

xd_arbiter.php

xd_arbiter.php

475 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

46 ms

badge_su.js

badge_su.js

141 ms

badges_su.css

badges_su.css

155 ms

css

css

88 ms

m_js_controller.js

m_js_controller.js

61 ms

abg.js

abg.js

77 ms

s_0RaXcM1FOu_395154613.html

s_0RaXcM1FOu_395154613.html

96 ms

jot

jot

126 ms

badgeRect50x60.png

badgeRect50x60.png

84 ms

favicon

favicon

67 ms

nessie_icon_tiamat_white.png

nessie_icon_tiamat_white.png

49 ms

s

s

36 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

52 ms

x_button_blue2.png

x_button_blue2.png

33 ms

adServer.bs

adServer.bs

128 ms

creative_add_on.js

creative_add_on.js

131 ms

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

2 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

31 ms

ebHtml5Banner.js

ebHtml5Banner.js

39 ms

F4-img-2_1.jpg

F4-img-2_1.jpg

4 ms

Accessibility Review

gutenbergnews.org accessibility score

67

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

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.

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

<frame> or <iframe> elements do not have a title

High

Form elements do not have associated labels

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

gutenbergnews.org SEO score

79

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

gutenbergnews.org

Open Graph data is detected on the main page of Gutenberg News. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: