Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

weby.ee

Auctions | WEBY.ee Auction

Page Load Speed

7.3 sec in total

First Response

2.4 sec

Resources Loaded

4.6 sec

Page Rendered

342 ms

weby.ee screenshot

About Website

Visit weby.ee now to see the best up-to-date WEBY content for Estonia and also check out these interesting facts you probably never knew about weby.ee

Oksjon.ee - Baltikumi suurim kindlustuse varade ja sõidukite oksjoni keskkond, oksjonid ettevõtetele ja eraisikutele. Avariilised autod!

Visit weby.ee

Key Findings

We analyzed Weby.ee page load time and found that the first response time was 2.4 sec and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

weby.ee performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

93/100

10%

LCP (Largest Contentful Paint)

Value12.0 s

0/100

25%

SI (Speed Index)

Value6.3 s

42/100

10%

TBT (Total Blocking Time)

Value1,880 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value12.4 s

14/100

10%

Network Requests Diagram

weby.ee

2360 ms

www.weby.ee

2000 ms

weby.png

241 ms

Our browser made a total of 3 requests to load all elements on the main page. We found that all of those requests were addressed to Weby.ee and no external sources were called. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Weby.ee.

Page Optimization Overview & Recommendations

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

Content Size

6.1 kB

After Optimization

4.8 kB

In fact, the total size of Weby.ee main page is 6.1 kB. This result falls within a big category (top 100 000) of medium weight web pages. Only a small number of websites need less resources to load. Images take 5.7 kB which makes up the majority of the site volume.

HTML Optimization

-34%

Potential reduce by 112 B

  • Original 326 B
  • After minification 319 B
  • After compression 214 B

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 112 B or 34% of the original size.

Image Optimization

-19%

Potential reduce by 1.1 kB

  • Original 5.7 kB
  • After minification 4.6 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. Obviously, WEBY needs image optimization as it can save up to 1.1 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

Requests Breakdown

We found no issues to fix!

Requests Now

1

After Optimization

1

The browser has sent 1 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WEBY. According to our analytics all requests are already optimized.

Accessibility Review

weby.ee accessibility score

79

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

High

Form elements do not have associated labels

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

weby.ee best practices score

58

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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

weby.ee SEO score

77

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Weby.ee 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 Weby.ee 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 description is not detected on the main page of WEBY. 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: