Access chartex.net. چارتکس - Chartex | نرم افزار رزرواسیون آژانس های مسافرتی

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value20.8 s

0/100

10%

TBT (Total Blocking Time)

Value160 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0.14

79/100

15%

TTI (Time to Interactive)

Value3.6 s

91/100

10%

chartex.net

375 ms

chartex.net

2622 ms

jquery.min.js

786 ms

multislider.min.js

474 ms

style-wpzoom-social-icons.css

479 ms

Our browser made a total of 128 requests to load all elements on the main page. We found that 94% of them (120 requests) were addressed to the original Chartex.net, 5% (6 requests) were made to Cdn.chartex.net and 1% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Chartex.net.

Content Size

2.6 MB

After Optimization

1.7 MB

In fact, the total size of Chartex.net main page is 2.6 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.8 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 209.6 kB

Original 266.2 kB
After minification 249.1 kB
After compression 56.6 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 209.6 kB or 79% of the original size.

Image Optimization

-30%

Potential reduce by 556.8 kB

Original 1.8 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. Obviously, Chartex needs image optimization as it can save up to 556.8 kB or 30% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-27%

Potential reduce by 83.0 kB

Original 307.5 kB
After minification 307.5 kB
After compression 224.5 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 83.0 kB or 27% of the original size.

CSS Optimization

-35%

Potential reduce by 72.4 kB

Original 204.1 kB
After minification 203.8 kB
After compression 131.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. Chartex.net needs all CSS files to be minified and compressed as it can save up to 72.4 kB or 35% of the original size.

Requests Now

124

After Optimization

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

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 the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

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

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Chartex.net can be misinterpreted by Google and other search engines. Our service has detected that Persian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Chartex.net 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

chartex.net

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

Report Summary

Performance

Accessibility

Best Practices

SEO

چارتکس - Chartex | نرم افزار رزرواسیون آژانس های مسافرتی

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

chartex.net

chartex.net

jquery.min.js

multislider.min.js

style-wpzoom-social-icons.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

chartex.net

chartex.net

jquery.min.js

multislider.min.js

style-wpzoom-social-icons.css

style.css

bootstrap.css

bootstrap-rtl.css

style.css

elder.css

wpzoom-socicon.css

wpzoom-social-icons-styles.css

js_composer.min.css

jquery.min.js

jquery-migrate.min.js

animate.css

modal-box.css

component-update.css

fronted-bootstrap.css

formreset.min.css

formsmain.min.css

readyclass.min.css

browsers.min.css

rtl.min.css

animate.min.css

page-scroll-to-id.min.js

bootstrap.min.js

main.js

social-icons-widget-frontend.js

modernizr.custom.js

classie.js

cssParser.js

js_composer_front.min.js

jquery.maskedinput.min.js

placeholders.jquery.min.js

core.min.js

jquery.json.min.js

gravityforms.min.js

jalali-datepicker.min.js

akismet-frontend.js

vc-waypoints.min.js

wp-emoji-release.min.js

Group-7166-4.png