60.9 sec in total
323 ms
60 sec
643 ms
Visit eepil.com now to see the best up-to-date Eepil content for Iran and also check out these interesting facts you probably never knew about eepil.com
Visit eepil.comWe analyzed Eepil.com page load time and found that the first response time was 323 ms and then it took 60.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 16 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
eepil.com performance score
name
value
score
weighting
Value6.9 s
1/100
10%
Value10.7 s
0/100
25%
Value20.8 s
0/100
10%
Value500 ms
58/100
30%
Value0.042
99/100
15%
Value18.0 s
3/100
10%
323 ms
4778 ms
16365 ms
640 ms
58 ms
Our browser made a total of 125 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Eepil.com, 94% (118 requests) were made to Eepil.ir and 2% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (20.2 sec) relates to the external source Eepil.ir.
Page size can be reduced by 1.3 MB (60%)
2.2 MB
874.1 kB
In fact, the total size of Eepil.com main page is 2.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 810.0 kB which makes up the majority of the site volume.
Potential reduce by 78.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 78.6 kB or 80% of the original size.
Potential reduce by 52.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. Eepil images are well optimized though.
Potential reduce by 566.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 566.4 kB or 70% of the original size.
Potential reduce by 640.5 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. Eepil.com needs all CSS files to be minified and compressed as it can save up to 640.5 kB or 86% of the original size.
Number of requests can be reduced by 55 (57%)
97
42
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eepil. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 26 to 1 for CSS and as a result speed up the page load time.
eepil.com
323 ms
www.eepil.ir
4778 ms
eepil.ir
16365 ms
fonts.css
640 ms
css
58 ms
styles.css
463 ms
styles-rtl.css
459 ms
css
125 ms
ninja-contact-form.css
1453 ms
flipbook.style.css
836 ms
font-awesome.css
998 ms
css
318 ms
userpro-rtl.min.css
1581 ms
lightview.css
1206 ms
userpro-jquery-ui.css
1481 ms
style.css
2324 ms
grid.css
1059 ms
base.css
1534 ms
layout.css
2575 ms
shortcodes.css
5919 ms
magnific-popup.css
2986 ms
mediaelementplayer.css
3213 ms
rtl.css
3217 ms
enfold.css
6343 ms
wp-emoji-release.min.js
4003 ms
custom.css
2862 ms
layerslider.css
3031 ms
userpro-msg.css
3045 ms
jquery.mCustomScrollbar.css
3496 ms
jquery.js
4894 ms
jquery-migrate.min.js
3463 ms
ninja-contact-form.min.js
4713 ms
flipbook.min.js
5776 ms
embed.js
3859 ms
avia-compat.js
4045 ms
greensock.js
5775 ms
layerslider.kreaturamedia.jquery.js
6426 ms
layerslider.transitions.js
5350 ms
userpro-msg.js
5785 ms
jquery.textareaAutoResize.js
5764 ms
jquery.mousewheel.min.js
6042 ms
jquery.mCustomScrollbar.min.js
6668 ms
userpro-social.min.js
6040 ms
jquery.form.min.js
3863 ms
scripts.js
3840 ms
core.min.js
3857 ms
datepicker.min.js
4765 ms
swfobject.js
4089 ms
spinners.min.js
3899 ms
lightview.js
5674 ms
scripts.min.js
16921 ms
performance.js
4070 ms
avia.js
7939 ms
shortcodes.js
6945 ms
jquery.magnific-popup.min.js
5996 ms
mediaelement-and-player.min.js
6828 ms
wp-mediaelement.js
5620 ms
comment-reply.min.js
5860 ms
wp-embed.min.js
5948 ms
bg_body.png
2887 ms
close.png
2394 ms
closeblack.png
2509 ms
blur4.jpg
4201 ms
ncf_userpic1.jpeg
3362 ms
header1.gif
3183 ms
blank.gif
3072 ms
21.jpg
8868 ms
22.jpg
10062 ms
farsi-300x81.png
3828 ms
rezome-2-300x81.png
4282 ms
17025-1-300x81.png
4273 ms
az-1-300x81.png
4913 ms
english.jpg
5581 ms
IMG_0462-31.jpg
8948 ms
23-492x423.jpg
7175 ms
show-image.png
7335 ms
loading.gif
7373 ms
Contact-180x180.jpg
7791 ms
shutterstock_13477333-180x180.jpg
7649 ms
1212-180x180.jpg
9087 ms
binder-for-orders1-180x180.jpg
8229 ms
wpyar-BNazanin.woff
9021 ms
photo_2016-01-20_20-53-03.jpg
8941 ms
freccia_dx_shorcuts_minibalck.png
9067 ms
pattern.png
10369 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
217 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
673 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
579 ms
wpyar-BTitrBold.woff
9407 ms
entypo-fontello.woff
8712 ms
fontawesome-webfont.woff
8427 ms
fontawesome-webfont.woff
9214 ms
unchecked-checkbox.png
8269 ms
Capture.jpg
8550 ms
print.css
675 ms
skin.css
500 ms
ajax-loader.gif
213 ms
sprite.png
896 ms
ncf_icons.svg
286 ms
951-2.jpg
4159 ms
atex.jpg
14294 ms
12345.png
248 ms
1222.png
187 ms
151.png
404 ms
30.jpg
8912 ms
lv.jpg
11231 ms
Ph.jpg
14503 ms
fhkjhnm.jpg
16012 ms
IMG_0018-400.jpg
20233 ms
IMG_0085-200.jpg
20232 ms
ghfdhxdj.jpg
19980 ms
IMG_0149-yjhg1.jpg
20233 ms
IMG_0099-3-00012.jpg
20232 ms
IMG_0424-ygh1.jpg
20233 ms
lokiujyhtgfr.jpg
20232 ms
cfgfh.jpg
20233 ms
1.jpg
20233 ms
20130124_184823.jpg
20233 ms
20130124_185957.jpg
20233 ms
IMG_1373.jpg
20233 ms
IMG_1372.jpg
20233 ms
IMG_1375.jpg
20232 ms
IMG_1374.jpg
20233 ms
IMG_1368.jpg
20234 ms
loading.gif
19842 ms
eepil.com accessibility score
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
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
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.
eepil.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
eepil.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
FA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eepil.com 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 Eepil.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.
eepil.com
Open Graph description is not detected on the main page of Eepil. 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: