38.5 sec in total
1.4 sec
34.9 sec
2.3 sec
Click here to check amazing Eshel content for Iran. Otherwise, check out these important facts you probably never knew about eshel.ir
بعد ششم اشل, تولید کنندۀ پک های مینیاتوری و تک محصولی های مینیاتوری با کیفیت استاندارد اروپائی CE
Visit eshel.irWe analyzed Eshel.ir page load time and found that the first response time was 1.4 sec and then it took 37.2 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
eshel.ir performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value7.9 s
3/100
25%
Value19.4 s
0/100
10%
Value2,810 ms
3/100
30%
Value0.397
25/100
15%
Value11.6 s
18/100
10%
1350 ms
669 ms
1197 ms
20221 ms
1082 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 95% of them (58 requests) were addressed to the original Eshel.ir, 2% (1 request) were made to Webgozar.ir and 2% (1 request) were made to Engine.webgozar.ir. The less responsive or slowest element that took the longest time to load (20.2 sec) belongs to the original domain Eshel.ir.
Page size can be reduced by 279.0 kB (24%)
1.2 MB
906.4 kB
In fact, the total size of Eshel.ir main page is 1.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. 40% of websites need less resources to load. Images take 958.2 kB which makes up the majority of the site volume.
Potential reduce by 99.2 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 14.3 kB, which is 12% 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 99.2 kB or 85% of the original size.
Potential reduce by 88.6 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. Eshel images are well optimized though.
Potential reduce by 15.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 15.5 kB or 67% of the original size.
Potential reduce by 75.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. Eshel.ir needs all CSS files to be minified and compressed as it can save up to 75.7 kB or 86% of the original size.
Number of requests can be reduced by 7 (12%)
57
50
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eshel. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
eshel.ir
1350 ms
UserSheetFa.css
669 ms
ResponsiveStyleSheet.css
1197 ms
jquery-1.7.2.min.js
20221 ms
smooth-scroll.js
1082 ms
jquery.hoverIntent.minified.js
385 ms
slider.css
297 ms
jquery.flexslider-min.js
354 ms
owl.carousel.css
482 ms
owl.theme.css
490 ms
owl.carousel.js
714 ms
c.aspx
366 ms
HeaderTop.png
232 ms
Logo.png
246 ms
tr.png
231 ms
en.png
4532 ms
ar.png
631 ms
BasketBox.png
353 ms
Picuserlogin.png
381 ms
sepMenu.png
389 ms
arrowDown.png
422 ms
arrowDown2.gif
527 ms
_MG_4907.png
1975 ms
1.jpg
1437 ms
%D9%88%DB%8C%D9%84%D8%A7%DB%8C%20%DA%A9%D9%88%D9%87%D8%B3%D8%AA%D8%A7%D9%86%DB%8C.png
1773 ms
Barbaek%C3%BC.jpg
1010 ms
BoxIndex.png
1737 ms
SmartPicture.aspx
1292 ms
SmartPicture.aspx
1582 ms
SmartPicture.aspx
1727 ms
SmartPicture.aspx
1865 ms
SmartPicture.aspx
2077 ms
SmartPicture.aspx
2339 ms
SmartPicture.aspx
2146 ms
SmartPicture.aspx
2197 ms
SmartPicture.aspx
2230 ms
SmartPicture.aspx
2295 ms
SmartPicture.aspx
2461 ms
SmartPicture.aspx
2534 ms
SmartPicture.aspx
2637 ms
SmartPicture.aspx
2547 ms
SmartPicture.aspx
13638 ms
SmartPicture.aspx
2683 ms
SmartPicture.aspx
3522 ms
SmartPicture.aspx
4035 ms
SmartPicture.aspx
4037 ms
SmartPicture.aspx
3367 ms
SmartPicture.aspx
3929 ms
Yekan.woff
3475 ms
SmartPicture.aspx
4142 ms
SmartPicture.aspx
3816 ms
xstat.aspx
431 ms
SmartPicture.aspx
3771 ms
SmartPicture.aspx
3915 ms
SmartPicture.aspx
4100 ms
SearchBox.png
3894 ms
BoxTopIndex2.png
3939 ms
BoxTopIndex.png
3879 ms
Sprite.png
3534 ms
circlearr.png
3352 ms
b229747d-6997-4f9d-99a2-3741d6a0a941
143 ms
eshel.ir accessibility score
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
eshel.ir best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
eshel.ir SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Document uses legible font sizes
Tap targets are not sized appropriately
FA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eshel.ir 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 Eshel.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.
eshel.ir
Open Graph description is not detected on the main page of Eshel. 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: