Tools & Wizards About Us
pos.ee screenshot

Report Summary

  • 68

    Performance

    Renders faster than
    80% of other websites

  • 56

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 46

    SEO

    Google-friendlier than
    18% of websites

pos.ee

» KAALUD, KASSASAHTLID, KASSAAPARAAT, HINNAPÜSTOL

Page Load Speed

2.7 sec in total

First Response

556 ms

Resources Loaded

1.9 sec

Page Rendered

246 ms

pos.ee screenshot

About Website

Click here to check amazing Pos content for Estonia. Otherwise, check out these important facts you probably never knew about pos.ee

Kaalud_kassaaparaat_hinnapustol

Visit pos.ee

Key Findings

We analyzed Pos.ee page load time and found that the first response time was 556 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

pos.ee performance score

68

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

60/100

10%

LCP (Largest Contentful Paint)

Value6.2 s

11/100

25%

SI (Speed Index)

Value4.1 s

80/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.147

77/100

15%

TTI (Time to Interactive)

Value3.2 s

95/100

10%

Network Requests Diagram

pos.ee

556 ms

style.css

118 ms

AC_RunActiveContent.js

221 ms

shadowbox.js

355 ms

shadowbox.css

235 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 95% of them (35 requests) were addressed to the original Pos.ee, 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (968 ms) belongs to the original domain Pos.ee.

Page Optimization Overview & Recommendations

Page size can be reduced by 135.1 kB (33%)

Content Size

411.9 kB

After Optimization

276.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pos.ee main page is 411.9 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. 30% of websites need less resources to load. Images take 266.9 kB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 41.9 kB

  • Original 45.9 kB
  • After minification 21.1 kB
  • After compression 4.0 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.8 kB, which is 54% 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 41.9 kB or 91% of the original size.

Image Optimization

-12%

Potential reduce by 33.1 kB

  • Original 266.9 kB
  • After minification 233.8 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, Pos needs image optimization as it can save up to 33.1 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-58%

Potential reduce by 51.9 kB

  • Original 89.2 kB
  • After minification 86.0 kB
  • After compression 37.3 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 51.9 kB or 58% of the original size.

CSS Optimization

-82%

Potential reduce by 8.1 kB

  • Original 9.9 kB
  • After minification 8.2 kB
  • After compression 1.8 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. Pos.ee needs all CSS files to be minified and compressed as it can save up to 8.1 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (42%)

Requests Now

36

After Optimization

21

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pos.ee

pos.ee

556 ms

style.css

style.css

118 ms

AC_RunActiveContent.js

AC_RunActiveContent.js

221 ms

shadowbox.js

shadowbox.js

355 ms

shadowbox.css

shadowbox.css

235 ms

bg.jpg

bg.jpg

119 ms

top.jpg

top.jpg

219 ms

split.png

split.png

119 ms

act1.png

act1.png

121 ms

act2.png

act2.png

221 ms

act3.png

act3.png

290 ms

logo.jpg

logo.jpg

233 ms

body1.png

body1.png

233 ms

body2.png

body2.png

238 ms

sub.jpg

sub.jpg

328 ms

tab.jpg

tab.jpg

330 ms

nool.gif

nool.gif

349 ms

238_1143QQ.jpg

238_1143QQ.jpg

465 ms

ER_foto1.jpg

ER_foto1.jpg

355 ms

button1.png

button1.png

402 ms

button2.png

button2.png

436 ms

print.jpg

print.jpg

437 ms

button3.png

button3.png

464 ms

tab_grey.jpg

tab_grey.jpg

473 ms

CAS_pb_.jpg

CAS_pb_.jpg

516 ms

soodus.jpg

soodus.jpg

654 ms

image%20from%20CHD_6800_EN%20J.jpg

image%20from%20CHD_6800_EN%20J.jpg

655 ms

open2612.jpg

open2612.jpg

694 ms

goods_238528.jpg

goods_238528.jpg

695 ms

DP-2268-500x50011.JPG

DP-2268-500x50011.JPG

590 ms

MTX05f-4%205.JPG

MTX05f-4%205.JPG

627 ms

Kaaluetikett5840%5B1%5D.jpg

Kaaluetikett5840%5B1%5D.jpg

708 ms

footer.png

footer.png

968 ms

line.png

line.png

762 ms

blank.gif

blank.gif

765 ms

ga.js

ga.js

6 ms

__utm.gif

__utm.gif

12 ms

Accessibility Review

pos.ee accessibility score

56

Accessibility Issues

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

High

<object> elements do not have alternate text

Best Practices

pos.ee best practices score

75

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

SEO Factors

pos.ee SEO score

46

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

High

robots.txt is not valid

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

High

Document uses plugins

Language and Encoding

  • Language Detected

    N/A

  • 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 Pos.ee can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Pos.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

pos.ee

Open Graph description is not detected on the main page of Pos. 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: