Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

webgui.org

WordPress vs Other Content Management Systems - Namecheap

Page Load Speed

2.7 sec in total

First Response

64 ms

Resources Loaded

1.6 sec

Page Rendered

1 sec

webgui.org screenshot

About Website

Visit webgui.org now to see the best up-to-date Webgui content for Russia and also check out these interesting facts you probably never knew about webgui.org

How does Wordpress stack up to other content management systems? Find out with Namecheap’s guide!

Visit webgui.org

Key Findings

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

Performance Metrics

webgui.org performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value7.2 s

5/100

25%

SI (Speed Index)

Value5.0 s

63/100

10%

TBT (Total Blocking Time)

Value1,970 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.7 s

8/100

10%

Network Requests Diagram

webgui.org

64 ms

wordpress-vs-other-content-management-systems

222 ms

195 ms

v1196.global-style.min.css

157 ms

UserHashDataLayer.ashx

120 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Webgui.org, 71% (32 requests) were made to Files.namecheap.com and 7% (3 requests) were made to Namecheap.com. The less responsive or slowest element that took the longest time to load (871 ms) relates to the external source Files.namecheap.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 132.3 kB (18%)

Content Size

715.5 kB

After Optimization

583.2 kB

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

HTML Optimization

-79%

Potential reduce by 131.2 kB

  • Original 166.6 kB
  • After minification 142.2 kB
  • After compression 35.4 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 24.4 kB, which is 15% 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 131.2 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 1.1 kB

  • Original 218.2 kB
  • After minification 217.1 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. Webgui images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 44 B

  • Original 241.6 kB
  • After minification 241.6 kB
  • After compression 241.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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 89.2 kB
  • After minification 89.2 kB
  • After compression 89.2 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. Webgui.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 7 (21%)

Requests Now

34

After Optimization

27

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

Accessibility Review

webgui.org accessibility score

95

Accessibility Issues

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.

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

Best Practices

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

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

webgui.org SEO score

93

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

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Webgui.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Webgui.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 Webgui. 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: