Report Summary

  • 52

    Performance

    Renders faster than
    69% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 91% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

ru.gg

Без труда сделать свою веб-страницу - 100% бесплатно! | Homepage-Konstruktor.ru

Page Load Speed

3.3 sec in total

First Response

507 ms

Resources Loaded

2.6 sec

Page Rendered

195 ms

ru.gg screenshot

About Website

Click here to check amazing Ru content for Ukraine. Otherwise, check out these important facts you probably never knew about ru.gg

lll➤ Cоздать бесплатный сайт с Homepage-Konstruktor.ru ✅ Без подготовки ✓ GDPR-модуль ✓ Много вариантов дизайна ✓ SEO. Зарегистрируйтесь бесплатно!

Visit ru.gg

Key Findings

We analyzed Ru.gg page load time and found that the first response time was 507 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

ru.gg performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

18/100

25%

SI (Speed Index)

Value7.5 s

27/100

10%

TBT (Total Blocking Time)

Value250 ms

84/100

30%

CLS (Cumulative Layout Shift)

Value0.054

98/100

15%

TTI (Time to Interactive)

Value8.2 s

41/100

10%

Network Requests Diagram

ru.gg

507 ms

www.homepage-konstruktor.ru

535 ms

jquery-1.11.3.min.js

590 ms

main71.js

605 ms

bootstrap.min.css

614 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Ru.gg, 51% (18 requests) were made to Webme.com and 37% (13 requests) were made to Wtheme.webme.com. The less responsive or slowest element that took the longest time to load (645 ms) relates to the external source Wtheme.webme.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 56.2 kB (11%)

Content Size

497.0 kB

After Optimization

440.8 kB

In fact, the total size of Ru.gg main page is 497.0 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. 45% of websites need less resources to load. Images take 345.3 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 22.8 kB

  • Original 29.6 kB
  • After minification 25.2 kB
  • After compression 6.8 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 4.3 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 22.8 kB or 77% of the original size.

Image Optimization

-4%

Potential reduce by 12.7 kB

  • Original 345.3 kB
  • After minification 332.7 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. Ru images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 13.5 kB

  • Original 87.3 kB
  • After minification 87.3 kB
  • After compression 73.9 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 13.5 kB or 15% of the original size.

CSS Optimization

-21%

Potential reduce by 7.3 kB

  • Original 34.8 kB
  • After minification 34.8 kB
  • After compression 27.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. Ru.gg needs all CSS files to be minified and compressed as it can save up to 7.3 kB or 21% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (52%)

Requests Now

33

After Optimization

16

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

Accessibility Review

ru.gg accessibility score

97

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

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

Best Practices

ru.gg best practices score

67

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

ru.gg SEO score

69

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

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    RU

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ru.gg can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that Ru.gg main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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