Tools & Wizards About Us
tse.ee screenshot

Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 66

    SEO

    Google-friendlier than
    26% of websites

tse.ee

Nasdaq Baltic Stock Exchanges Home Page

Page Load Speed

3.2 sec in total

First Response

165 ms

Resources Loaded

2.7 sec

Page Rendered

329 ms

tse.ee screenshot

About Website

Welcome to tse.ee homepage info - get ready to check Tse best content for Russia right away, or after learning these important things about tse.ee

Nasdaq Baltic consists of stock exchanges in Tallinn, Riga and Vilnius. Monitor real time stock market data on our website.

Visit tse.ee

Key Findings

We analyzed Tse.ee page load time and found that the first response time was 165 ms and then it took 3 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

tse.ee performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

43/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value5.7 s

51/100

10%

TBT (Total Blocking Time)

Value320 ms

77/100

30%

CLS (Cumulative Layout Shift)

Value0.566

12/100

15%

TTI (Time to Interactive)

Value7.3 s

50/100

10%

Network Requests Diagram

tse.ee

165 ms

nasdaqbaltic.com

1073 ms

bootstrap.min.194.css

360 ms

swiper.min.194.css

356 ms

main.194.css

459 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Tse.ee, 61% (25 requests) were made to Nasdaqbaltic.com and 29% (12 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Nasdaqbaltic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 61.6 kB (2%)

Content Size

2.5 MB

After Optimization

2.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tse.ee main page is 2.5 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. 55% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 43.4 kB

  • Original 52.8 kB
  • After minification 47.0 kB
  • After compression 9.4 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 5.8 kB, which is 11% 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 43.4 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 13.4 kB

  • Original 2.2 MB
  • After minification 2.2 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. Tse images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 787 B

  • Original 237.3 kB
  • After minification 237.3 kB
  • After compression 236.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

-9%

Potential reduce by 4.0 kB

  • Original 46.2 kB
  • After minification 46.2 kB
  • After compression 42.2 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. Tse.ee has all CSS files already compressed.

Requests Breakdown

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

Requests Now

27

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tse.ee

tse.ee

165 ms

nasdaqbaltic.com

nasdaqbaltic.com

1073 ms

bootstrap.min.194.css

bootstrap.min.194.css

360 ms

swiper.min.194.css

swiper.min.194.css

356 ms

main.194.css

main.194.css

459 ms

modernizr.194.js

modernizr.194.js

373 ms

jquery-3.7.0.min.194.js

jquery-3.7.0.min.194.js

474 ms

bootstrap.bundle.min.194.js

bootstrap.bundle.min.194.js

475 ms

jquery.marquee.min.194.js

jquery.marquee.min.194.js

437 ms

js.cookie.194.js

js.cookie.194.js

556 ms

nasdaq_app.194.js

nasdaq_app.194.js

534 ms

js

js

51 ms

js

js

97 ms

highstock.194.js

highstock.194.js

726 ms

template7.min.194.js

template7.min.194.js

602 ms

swiper.min.194.js

swiper.min.194.js

641 ms

_Incapsula_Resource

_Incapsula_Resource

601 ms

css2

css2

30 ms

logo.svg

logo.svg

269 ms

search.svg

search.svg

283 ms

ico-menu.svg

ico-menu.svg

361 ms

ico-youtube-white.svg

ico-youtube-white.svg

363 ms

ico-sitemap.svg

ico-sitemap.svg

390 ms

ico-search-mobile.svg

ico-search-mobile.svg

422 ms

KFOkCnqEu92Fr1MmgWxPKTU1Kg.ttf

KFOkCnqEu92Fr1MmgWxPKTU1Kg.ttf

61 ms

KFOlCnqEu92Fr1MmSU5vAx0_IsE.ttf

KFOlCnqEu92Fr1MmSU5vAx0_IsE.ttf

90 ms

KFOmCnqEu92Fr1Me5WZNCzc.ttf

KFOmCnqEu92Fr1Me5WZNCzc.ttf

97 ms

KFOlCnqEu92Fr1MmEU9vAx0_IsE.ttf

KFOlCnqEu92Fr1MmEU9vAx0_IsE.ttf

116 ms

KFOlCnqEu92Fr1MmWUlvAx0_IsE.ttf

KFOlCnqEu92Fr1MmWUlvAx0_IsE.ttf

116 ms

KFOlCnqEu92Fr1MmYUtvAx0_IsE.ttf

KFOlCnqEu92Fr1MmYUtvAx0_IsE.ttf

113 ms

KFOjCnqEu92Fr1Mu51TjARc9AMP6lQ.ttf

KFOjCnqEu92Fr1Mu51TjARc9AMP6lQ.ttf

166 ms

KFOiCnqEu92Fr1Mu51QrIzcXKMny.ttf

KFOiCnqEu92Fr1Mu51QrIzcXKMny.ttf

116 ms

KFOkCnqEu92Fr1Mu52xPKTU1Kg.ttf

KFOkCnqEu92Fr1Mu52xPKTU1Kg.ttf

163 ms

KFOjCnqEu92Fr1Mu51S7ABc9AMP6lQ.ttf

KFOjCnqEu92Fr1Mu51S7ABc9AMP6lQ.ttf

165 ms

KFOjCnqEu92Fr1Mu51TzBhc9AMP6lQ.ttf

KFOjCnqEu92Fr1Mu51TzBhc9AMP6lQ.ttf

118 ms

KFOjCnqEu92Fr1Mu51TLBBc9AMP6lQ.ttf

KFOjCnqEu92Fr1Mu51TLBBc9AMP6lQ.ttf

163 ms

1-2-scaled.jpg

1-2-scaled.jpg

983 ms

rect-group-1.svg

rect-group-1.svg

414 ms

HERO1.jpg

HERO1.jpg

1000 ms

Tewox_for-Nasdaq-scaled.jpg

Tewox_for-Nasdaq-scaled.jpg

919 ms

_Incapsula_Resource

_Incapsula_Resource

104 ms

Accessibility Review

tse.ee accessibility score

91

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.

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

tse.ee SEO score

66

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

High

Document doesn't have a valid hreflang

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tse.ee can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Tse.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

tse.ee

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