Tools & Wizards About Us
testgutenberg.com screenshot

Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

testgutenberg.com

The new Gutenberg editing experience – WordPress.org

Page Load Speed

941 ms in total

First Response

35 ms

Resources Loaded

850 ms

Page Rendered

56 ms

testgutenberg.com screenshot

About Website

Welcome to testgutenberg.com homepage info - get ready to check Test Gutenberg best content for Iran right away, or after learning these important things about testgutenberg.com

A new editing experience for WordPress is in the works, code name Gutenberg. Read more about it and test it!

Visit testgutenberg.com

Key Findings

We analyzed Testgutenberg.com page load time and found that the first response time was 35 ms and then it took 906 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

testgutenberg.com performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value13.9 s

0/100

25%

SI (Speed Index)

Value14.0 s

1/100

10%

TBT (Total Blocking Time)

Value5,920 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.259

48/100

15%

TTI (Time to Interactive)

Value19.4 s

2/100

10%

Network Requests Diagram

testgutenberg.com

35 ms

186 ms

gtm.js

53 ms

style.css

70 ms

style.css

70 ms

Our browser made a total of 135 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Testgutenberg.com, 99% (133 requests) were made to Wordpress.org and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (243 ms) relates to the external source Wordpress.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (41%)

Content Size

3.1 MB

After Optimization

1.8 MB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Testgutenberg.com main page is 3.1 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. 55% of websites need less resources to load. Javascripts take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 1.2 MB

  • Original 1.4 MB
  • After minification 1.4 MB
  • After compression 141.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 1.2 MB or 90% of the original size.

JavaScript Optimization

-1%

Potential reduce by 21.1 kB

  • Original 1.5 MB
  • After minification 1.5 MB
  • After compression 1.5 MB

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 7.1 kB

  • Original 162.5 kB
  • After minification 162.0 kB
  • After compression 155.5 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. Testgutenberg.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 131 (98%)

Requests Now

133

After Optimization

2

  • JavaScript
  • CSS

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

Network Requests Diagram

testgutenberg.com

testgutenberg.com

35 ms

186 ms

gtm.js

gtm.js

53 ms

style.css

style.css

70 ms

style.css

style.css

70 ms

ponyfill.css

ponyfill.css

70 ms

buttons.min.css

buttons.min.css

87 ms

dashicons.min.css

dashicons.min.css

116 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

88 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

90 ms

media-views.min.css

media-views.min.css

96 ms

imgareaselect.css

imgareaselect.css

101 ms

editor.min.css

editor.min.css

108 ms

style.css

style.css

110 ms

style.css

style.css

114 ms

style.css

style.css

119 ms

style.css

style.css

123 ms

style.css

style.css

130 ms

style.css

style.css

137 ms

common.min.css

common.min.css

133 ms

forms.min.css

forms.min.css

136 ms

reset.css

reset.css

141 ms

content.css

content.css

145 ms

editor.css

editor.css

152 ms

style.css

style.css

154 ms

style.css

style.css

156 ms

style.css

style.css

156 ms

style.css

style.css

161 ms

style.css

style.css

165 ms

style.css

style.css

172 ms

style-editor.css

style-editor.css

175 ms

media.min.css

media.min.css

176 ms

admin-menu.min.css

admin-menu.min.css

177 ms

admin-bar.min.css

admin-bar.min.css

183 ms

l10n.min.css

l10n.min.css

186 ms

wp-polyfill.min.js

wp-polyfill.min.js

194 ms

react.min.js

react.min.js

197 ms

react-jsx-runtime.min.js

react-jsx-runtime.min.js

196 ms

index.min.js

index.min.js

136 ms

index.min.js

index.min.js

141 ms

index.min.js

index.min.js

143 ms

index.min.js

index.min.js

149 ms

index.min.js

index.min.js

138 ms

index.min.js

index.min.js

137 ms

react-dom.min.js

react-dom.min.js

155 ms

index.min.js

index.min.js

136 ms

index.min.js

index.min.js

136 ms

index.min.js

index.min.js

134 ms

index.min.js

index.min.js

132 ms

index.min.js

index.min.js

132 ms

index.min.js

index.min.js

140 ms

index.min.js

index.min.js

137 ms

index.min.js

index.min.js

143 ms

index.min.js

index.min.js

218 ms

index.min.js

index.min.js

132 ms

index.min.js

index.min.js

130 ms

index.min.js

index.min.js

138 ms

index.min.js

index.min.js

140 ms

index.min.js

index.min.js

140 ms

index.min.js

index.min.js

135 ms

index.min.js

index.min.js

165 ms

index.min.js

index.min.js

141 ms

index.min.js

index.min.js

145 ms

moment.min.js

moment.min.js

147 ms

index.min.js

index.min.js

150 ms

index.min.js

index.min.js

146 ms

index.min.js

index.min.js

147 ms

index.min.js

index.min.js

229 ms

index.min.js

index.min.js

158 ms

index.min.js

index.min.js

158 ms

index.min.js

index.min.js

150 ms

index.min.js

index.min.js

148 ms

index.min.js

index.min.js

176 ms

index.min.js

index.min.js

177 ms

index.min.js

index.min.js

176 ms

index.min.js

index.min.js

170 ms

index.min.js

index.min.js

243 ms

button.js

button.js

161 ms

link.js

link.js

167 ms

shared-modifications.js

shared-modifications.js

166 ms

jquery.min.js

jquery.min.js

162 ms

jquery-migrate.min.js

jquery-migrate.min.js

169 ms

underscore.min.js

underscore.min.js

170 ms

utils.min.js

utils.min.js

169 ms

backbone.min.js

backbone.min.js

173 ms

wp-util.min.js

wp-util.min.js

180 ms

wp-backbone.min.js

wp-backbone.min.js

178 ms

media-models.min.js

media-models.min.js

178 ms

moxie.min.js

moxie.min.js

175 ms

plupload.min.js

plupload.min.js

173 ms

wp-plupload.min.js

wp-plupload.min.js

178 ms

core.min.js

core.min.js

177 ms

mouse.min.js

mouse.min.js

199 ms

sortable.min.js

sortable.min.js

195 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

194 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

184 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

189 ms

api-request.min.js

api-request.min.js

181 ms

clipboard.min.js

clipboard.min.js

176 ms

media-views.min.js

media-views.min.js

174 ms

editor.min.js

editor.min.js

174 ms

index.min.js

index.min.js

199 ms

index.min.js

index.min.js

158 ms

index.min.js

index.min.js

156 ms

index.min.js

index.min.js

159 ms

index.min.js

index.min.js

165 ms

index.min.js

index.min.js

137 ms

index.min.js

index.min.js

149 ms

videopress-add-resumable-upload-support.js

videopress-add-resumable-upload-support.js

145 ms

index.min.js

index.min.js

186 ms

index.min.js

index.min.js

159 ms

index.min.js

index.min.js

152 ms

index.min.js

index.min.js

156 ms

postbox.min.js

postbox.min.js

156 ms

index.min.js

index.min.js

155 ms

index.js

index.js

152 ms

index.js

index.js

146 ms

editor-modifications.js

editor-modifications.js

166 ms

view.js

view.js

166 ms

heartbeat.min.js

heartbeat.min.js

162 ms

shortcode.min.js

shortcode.min.js

155 ms

media-editor.min.js

media-editor.min.js

151 ms

media-audiovideo.min.js

media-audiovideo.min.js

151 ms

quicktags.min.js

quicktags.min.js

152 ms

hoverIntent.min.js

hoverIntent.min.js

150 ms

common.min.js

common.min.js

146 ms

wplink.min.js

wplink.min.js

146 ms

menu.min.js

menu.min.js

123 ms

autocomplete.min.js

autocomplete.min.js

127 ms

thickbox.js

thickbox.js

130 ms

media-upload.min.js

media-upload.min.js

123 ms

index.min.js

index.min.js

124 ms

index.min.js

index.min.js

132 ms

tinymce.min.js

tinymce.min.js

178 ms

plugin.min.js

plugin.min.js

138 ms

Accessibility Review

testgutenberg.com accessibility score

98

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

testgutenberg.com 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

testgutenberg.com SEO score

100

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

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 Testgutenberg.com 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 Testgutenberg.com 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

testgutenberg.com

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