Access intex-site.com. شرکت آوان سپهر آمیتیس: فروش استخر پیش ساخته، تخت خواب تشک و قایق بادی

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

11/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value370 ms

71/100

30%

CLS (Cumulative Layout Shift)

Value0.653

8/100

15%

TTI (Time to Interactive)

Value8.2 s

40/100

10%

intex-site.com

2697 ms

font-awesome.min.css

640 ms

bootstrap.min.css

853 ms

bootstrap.min.js

644 ms

Style.css

644 ms

Our browser made a total of 141 requests to load all elements on the main page. We found that 99% of them (140 requests) were addressed to the original Intex-site.com, 1% (1 request) were made to Trustseal.enamad.ir. The less responsive or slowest element that took the longest time to load (3.9 sec) belongs to the original domain Intex-site.com.

Content Size

3.2 MB

After Optimization

1.5 MB

In fact, the total size of Intex-site.com main page is 3.2 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. 45% of websites need less resources to load. Javascripts take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 362.7 kB

Original 403.5 kB
After minification 330.5 kB
After compression 40.9 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 73.0 kB, which is 18% 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 362.7 kB or 90% of the original size.

Image Optimization

-3%

Potential reduce by 33.3 kB

Original 1.0 MB
After minification 993.8 kB

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

JavaScript Optimization

-74%

Potential reduce by 1.1 MB

Original 1.5 MB
After minification 1.4 MB
After compression 379.4 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 1.1 MB or 74% of the original size.

CSS Optimization

-85%

Potential reduce by 215.7 kB

Original 253.4 kB
After minification 190.3 kB
After compression 37.7 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. Intex-site.com needs all CSS files to be minified and compressed as it can save up to 215.7 kB or 85% of the original size.

Requests Now

134

After Optimization

The browser has sent 134 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Intex Site. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 13 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 keyboard navigation in your application.

High

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

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

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

High

Image elements do not have [alt] attributes

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 Intex-site.com 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 Intex-site.com 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

intex-site.com

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

شرکت آوان سپهر آمیتیس: فروش استخر پیش ساخته، تخت خواب تشک و قایق بادی

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

intex-site.com

font-awesome.min.css

bootstrap.min.css

bootstrap.min.js

Style.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

intex-site.com

font-awesome.min.css

bootstrap.min.css

bootstrap.min.js

Style.css

ClockCountDown.css

jquery.min.js

jquery-ui.min.js

jquery.canvasjs.min.js

jquery.lazyload.js

jssor.slider.mini.js

cssResposiveMenu.css

cssMenuscript.js

slick.css

slick-theme.css

slick.min.js

nivo-slider.css

jquery.bxslider.js

jquery.elevatezoom.js

products.css

jquery.bxslider.css

toTop.css

modernizr.js

Styles.css

jwplayer.js

jwplayer.html5.js

WebResource.axd

WebResource.axd

ScriptResource.axd

Telerik.Web.UI.WebResource.axd

jquery.nivo.slider.js

main.js

logo.aspx

register_gray.png

1021.jpg

1022.jpg

1023.jpg

8.jpg

7.jpg

10.jpg

9.jpg

31.jpg

22.jpg