1.7 sec in total
44 ms
1.6 sec
62 ms
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.comWe analyzed Testgutenberg.com page load time and found that the first response time was 44 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
testgutenberg.com performance score
name
value
score
weighting
Value12.6 s
0/100
10%
Value13.8 s
0/100
25%
Value20.5 s
0/100
10%
Value8,980 ms
0/100
30%
Value0.426
22/100
15%
Value24.4 s
0/100
10%
44 ms
511 ms
54 ms
116 ms
133 ms
Our browser made a total of 134 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Testgutenberg.com, 98% (131 requests) were made to Wordpress.org and 1% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (511 ms) relates to the external source Wordpress.org.
Page size can be reduced by 1.5 MB (45%)
3.2 MB
1.8 MB
In fact, the total size of Testgutenberg.com main page is 3.2 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 1.8 MB which makes up the majority of the site volume.
Potential reduce by 1.2 MB
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.
Potential reduce by 279.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 279.5 kB or 16% of the original size.
Potential reduce by 3.7 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.
Number of requests can be reduced by 130 (98%)
132
2
The browser has sent 132 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 31 to 1 for CSS and as a result speed up the page load time.
testgutenberg.com
44 ms
511 ms
gtm.js
54 ms
style.css
116 ms
style.css
133 ms
ponyfill.css
142 ms
buttons.min.css
155 ms
dashicons.min.css
200 ms
mediaelementplayer-legacy.min.css
163 ms
wp-mediaelement.min.css
163 ms
media-views.min.css
164 ms
imgareaselect.css
169 ms
editor.min.css
184 ms
style.css
195 ms
style.css
200 ms
style.css
194 ms
style.css
199 ms
style.css
214 ms
common.min.css
230 ms
forms.min.css
226 ms
reset.css
222 ms
content.css
223 ms
editor.css
233 ms
style.css
243 ms
style.css
252 ms
style.css
250 ms
style.css
256 ms
style.css
259 ms
style.css
261 ms
style-editor.css
272 ms
media.min.css
278 ms
admin-menu.min.css
280 ms
admin-bar.min.css
286 ms
l10n.min.css
289 ms
wp-polyfill-inert.min.js
295 ms
regenerator-runtime.min.js
302 ms
wp-polyfill.min.js
335 ms
react.min.js
307 ms
index.min.js
211 ms
index.min.js
203 ms
index.min.js
196 ms
index.min.js
196 ms
index.min.js
211 ms
index.min.js
203 ms
react-dom.min.js
317 ms
index.min.js
202 ms
index.min.js
307 ms
index.min.js
290 ms
index.min.js
281 ms
index.min.js
281 ms
index.min.js
325 ms
index.min.js
329 ms
index.min.js
325 ms
index.min.js
326 ms
index.min.js
324 ms
index.min.js
326 ms
index.min.js
324 ms
index.min.js
333 ms
index.min.js
318 ms
index.min.js
309 ms
index.min.js
303 ms
index.min.js
310 ms
moment.min.js
345 ms
index.min.js
303 ms
index.min.js
301 ms
index.min.js
339 ms
index.min.js
339 ms
index.min.js
453 ms
index.min.js
329 ms
index.min.js
322 ms
destination
59 ms
index.min.js
316 ms
index.min.js
320 ms
index.min.js
340 ms
index.min.js
331 ms
index.min.js
325 ms
index.min.js
329 ms
index.min.js
397 ms
button.js
315 ms
link.js
318 ms
shared-modifications.js
317 ms
jquery.min.js
225 ms
jquery-migrate.min.js
229 ms
underscore.min.js
236 ms
utils.min.js
238 ms
backbone.min.js
211 ms
wp-util.min.js
206 ms
wp-backbone.min.js
267 ms
media-models.min.js
256 ms
moxie.min.js
259 ms
plupload.min.js
251 ms
wp-plupload.min.js
251 ms
core.min.js
248 ms
mouse.min.js
250 ms
sortable.min.js
268 ms
mediaelement-and-player.min.js
272 ms
mediaelement-migrate.min.js
264 ms
wp-mediaelement.min.js
272 ms
api-request.min.js
274 ms
clipboard.min.js
237 ms
media-views.min.js
228 ms
editor.min.js
239 ms
index.min.js
250 ms
index.min.js
243 ms
index.min.js
243 ms
index.min.js
237 ms
index.min.js
238 ms
index.min.js
237 ms
videopress-add-resumable-upload-support.js
228 ms
index.min.js
226 ms
index.min.js
337 ms
index.min.js
230 ms
index.min.js
206 ms
index.min.js
201 ms
postbox.min.js
206 ms
index.min.js
204 ms
index.js
208 ms
index.js
198 ms
editor-modifications.js
201 ms
view.js
187 ms
heartbeat.min.js
202 ms
shortcode.min.js
205 ms
media-editor.min.js
149 ms
media-audiovideo.min.js
148 ms
quicktags.min.js
152 ms
wplink.min.js
165 ms
menu.min.js
168 ms
autocomplete.min.js
169 ms
thickbox.js
159 ms
media-upload.min.js
158 ms
index.min.js
208 ms
index.min.js
196 ms
tinymce.min.js
226 ms
plugin.min.js
198 ms
testgutenberg.com accessibility score
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
Links do not have a discernible name
testgutenberg.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
testgutenberg.com SEO score
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
Document uses legible font sizes
EN
EN
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.
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: