Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 53% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

amps.ee

Amps | Kohvikud Tallinnas, catering, päevapakkumised

Page Load Speed

10.2 sec in total

First Response

398 ms

Resources Loaded

7.9 sec

Page Rendered

1.9 sec

amps.ee screenshot

About Website

Welcome to amps.ee homepage info - get ready to check Amps best content for Estonia right away, or after learning these important things about amps.ee

Amps kohvikud Tallinnas toovad külastajateni maitsvad päevapakkumised, põnevad catering menüüd, hõrgu a la carte menüü ja põnevad hooajamenüüd. Tule külla!

Visit amps.ee

Key Findings

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

Performance Metrics

amps.ee performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value7.6 s

4/100

25%

SI (Speed Index)

Value7.6 s

26/100

10%

TBT (Total Blocking Time)

Value300 ms

79/100

30%

CLS (Cumulative Layout Shift)

Value0.223

56/100

15%

TTI (Time to Interactive)

Value9.3 s

31/100

10%

Network Requests Diagram

amps.ee

398 ms

amps.ee

3372 ms

script.js

193 ms

sbi-styles.min.css

293 ms

frontend.css

329 ms

Our browser made a total of 162 requests to load all elements on the main page. We found that 88% of them (143 requests) were addressed to the original Amps.ee, 10% (16 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Cdn-cookieyes.com. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Amps.ee.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (12%)

Content Size

8.3 MB

After Optimization

7.3 MB

In fact, the total size of Amps.ee main page is 8.3 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only a small number of websites need less resources to load. Images take 7.3 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 263.2 kB

  • Original 312.7 kB
  • After minification 288.7 kB
  • After compression 49.5 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 263.2 kB or 84% of the original size.

Image Optimization

-10%

Potential reduce by 746.5 kB

  • Original 7.3 MB
  • After minification 6.6 MB

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. Amps images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.7 kB

  • Original 449.9 kB
  • After minification 449.9 kB
  • After compression 448.2 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

-3%

Potential reduce by 6.0 kB

  • Original 238.1 kB
  • After minification 237.9 kB
  • After compression 232.0 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. Amps.ee has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 98 (71%)

Requests Now

139

After Optimization

41

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

Accessibility Review

amps.ee accessibility score

82

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

amps.ee best practices score

83

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

Page has valid source maps

SEO Factors

amps.ee 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

    ET

  • Language Claimed

    ET

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Amps.ee can be misinterpreted by Google and other search engines. Our service has detected that Estonian is used on the page, and it matches the claimed language. Our system also found out that Amps.ee 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 data is detected on the main page of Amps. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: