Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 0

    Best Practices

  • 0

    SEO

myticket.ro

myticket.ro - Cumpara bilete online la ultimele evenimente

Page Load Speed

6.2 sec in total

First Response

487 ms

Resources Loaded

5.4 sec

Page Rendered

374 ms

myticket.ro screenshot

About Website

Click here to check amazing Myticket content for Romania. Otherwise, check out these important facts you probably never knew about myticket.ro

Cumpara bilete online la ultimele evenimente

Visit myticket.ro

Key Findings

We analyzed Myticket.ro page load time and found that the first response time was 487 ms and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

myticket.ro performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value7.6 s

3/100

25%

SI (Speed Index)

Value7.6 s

25/100

10%

TBT (Total Blocking Time)

Value150 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value1.134

1/100

15%

TTI (Time to Interactive)

Value11.2 s

20/100

10%

Network Requests Diagram

myticket.ro

487 ms

www.myticket.ro

1338 ms

style.css

377 ms

slideshow.css

388 ms

jquery.js

807 ms

Our browser made a total of 128 requests to load all elements on the main page. We found that 46% of them (59 requests) were addressed to the original Myticket.ro, 33% (42 requests) were made to Mytimg.ro and 9% (12 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.8 sec) relates to the external source Mytimg.ro.

Page Optimization Overview & Recommendations

Page size can be reduced by 546.8 kB (27%)

Content Size

2.0 MB

After Optimization

1.5 MB

In fact, the total size of Myticket.ro main page is 2.0 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. 60% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 57.6 kB

  • Original 68.4 kB
  • After minification 58.9 kB
  • After compression 10.8 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 9.5 kB, which is 14% 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 57.6 kB or 84% of the original size.

Image Optimization

-6%

Potential reduce by 84.2 kB

  • Original 1.4 MB
  • After minification 1.3 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. Myticket images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 337.0 kB

  • Original 490.2 kB
  • After minification 466.3 kB
  • After compression 153.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 337.0 kB or 69% of the original size.

CSS Optimization

-85%

Potential reduce by 67.9 kB

  • Original 79.9 kB
  • After minification 66.9 kB
  • After compression 12.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. Myticket.ro needs all CSS files to be minified and compressed as it can save up to 67.9 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (25%)

Requests Now

126

After Optimization

95

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

Accessibility Review

myticket.ro accessibility score

65

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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.

SEO Factors

myticket.ro SEO score

0

Language and Encoding

  • Language Detected

    RO

  • Language Claimed

    RO

  • Encoding

    UTF-8

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