Access ticketcharter.ir. خرید بلیط هواپیما چارتر | بلیط چارتر هواپیما

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value5.7 s

17/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value1,150 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value7.1 s

52/100

10%

ticketcharter.ir

727 ms

ticket-charter.com

973 ms

reset.css

268 ms

main.css

269 ms

responsive.css

268 ms

Our browser made a total of 14 requests to load all elements on the main page. We found that 7% of them (1 request) were addressed to the original Ticketcharter.ir, 86% (12 requests) were made to Cdn.charter725.ir and 7% (1 request) were made to Ticket-charter.com. The less responsive or slowest element that took the longest time to load (973 ms) relates to the external source Ticket-charter.com.

Content Size

200.5 kB

After Optimization

23.0 kB

In fact, the total size of Ticketcharter.ir main page is 200.5 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. Only 10% of websites need less resources to load. HTML takes 200.5 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 177.6 kB

Original 200.5 kB
After minification 130.4 kB
After compression 23.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 70.1 kB, which is 35% 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 177.6 kB or 89% of the original size.

Requests Now

After Optimization

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

[id] attributes on active, focusable elements are not unique

High

Some elements have a [tabindex] value greater than 0

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.

High

Links do not have a discernible name

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

Low

Detected JavaScript libraries

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

FA
Language Claimed

FA
Encoding

UTF-8

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