Report Summary

  • 97

    Performance

    Renders faster than
    94% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

velomobile.org

Сайт для тех, кто хочет сделать веломобиль, трайк, лигерад

Page Load Speed

22.3 sec in total

First Response

374 ms

Resources Loaded

21.8 sec

Page Rendered

159 ms

velomobile.org screenshot

About Website

Welcome to velomobile.org homepage info - get ready to check Velomobile best content for Russia right away, or after learning these important things about velomobile.org

Обзор и обсуждение транспортных средств с мускульным приводом, таких как веломобиль и лигерад, а так же их самостоятельное проектирование и изготовление

Visit velomobile.org

Key Findings

We analyzed Velomobile.org page load time and found that the first response time was 374 ms and then it took 21.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

velomobile.org performance score

97

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

91/100

10%

LCP (Largest Contentful Paint)

Value2.1 s

96/100

25%

SI (Speed Index)

Value2.6 s

97/100

10%

TBT (Total Blocking Time)

Value90 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.035

100/100

15%

TTI (Time to Interactive)

Value2.7 s

97/100

10%

Network Requests Diagram

velomobile.org

374 ms

velomobile.org

650 ms

system.css

132 ms

general.css

263 ms

template.css

349 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 73% of them (37 requests) were addressed to the original Velomobile.org, 8% (4 requests) were made to Rf.revolvermaps.com and 4% (2 requests) were made to Counter.rambler.ru. The less responsive or slowest element that took the longest time to load (19.7 sec) relates to the external source Hit37.hotlog.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 39.2 kB (20%)

Content Size

194.2 kB

After Optimization

155.0 kB

In fact, the total size of Velomobile.org main page is 194.2 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. 20% of websites need less resources to load. Images take 73.1 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 32.2 kB

  • Original 41.5 kB
  • After minification 39.4 kB
  • After compression 9.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 32.2 kB or 78% of the original size.

Image Optimization

-4%

Potential reduce by 2.7 kB

  • Original 73.1 kB
  • After minification 70.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. Velomobile images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 2.2 kB

  • Original 66.8 kB
  • After minification 66.8 kB
  • After compression 64.6 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

-17%

Potential reduce by 2.1 kB

  • Original 12.8 kB
  • After minification 12.8 kB
  • After compression 10.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. Velomobile.org needs all CSS files to be minified and compressed as it can save up to 2.1 kB or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (53%)

Requests Now

43

After Optimization

20

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

Accessibility Review

velomobile.org accessibility score

79

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.

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

velomobile.org best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

velomobile.org SEO score

62

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

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Velomobile.org 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 Velomobile.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 Velomobile. 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: