8.9 sec in total
1.3 sec
7.4 sec
168 ms
Click here to check amazing Pec content for Iran. Otherwise, check out these important facts you probably never knew about pec.ir
شرکت تجارت الکترونیک پارسیان، شرکت سهامی عام است که وابسته بانک پارسیان می باشد که در زمینه خدمات نرمافزاری، تجارت الکترونیک ، خدمات کارت، پرداخت اینترنتی و دستگاه کارتخوان فعالیت دارد
Visit pec.irWe analyzed Pec.ir page load time and found that the first response time was 1.3 sec and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster. This domain responded with an error, which can significantly jeopardize Pec.ir rating and web reputation
pec.ir performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value9.5 s
0/100
25%
Value17.7 s
0/100
10%
Value640 ms
46/100
30%
Value0.444
21/100
15%
Value10.4 s
24/100
10%
1311 ms
2804 ms
406 ms
393 ms
399 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that all of those requests were addressed to Pec.ir and no external sources were called. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Pec.ir.
Page size can be reduced by 455.4 kB (53%)
854.7 kB
399.3 kB
In fact, the total size of Pec.ir main page is 854.7 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. 40% of websites need less resources to load. Javascripts take 404.5 kB which makes up the majority of the site volume.
Potential reduce by 74.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. 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 74.2 kB or 79% of the original size.
Potential reduce by 51.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. Obviously, Pec needs image optimization as it can save up to 51.6 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 296.9 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 296.9 kB or 73% of the original size.
Potential reduce by 32.6 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. Pec.ir needs all CSS files to be minified and compressed as it can save up to 32.6 kB or 85% of the original size.
Number of requests can be reduced by 22 (47%)
47
25
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pec. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
pec.ir
1311 ms
Default.aspx
2804 ms
LinkMenu_js
406 ms
Comment_js
393 ms
Menu_js
399 ms
Portal_css
371 ms
Jquery_js
652 ms
Jqueryui_js
836 ms
Webparts_js
578 ms
player_js
589 ms
Style.aspx
598 ms
Comment_css
586 ms
WebResource.axd
792 ms
ScriptResource.axd
791 ms
ScriptResource.axd
794 ms
style.css
817 ms
jquery.js
920 ms
jquery.slimscroll.min.js
1045 ms
jquery.fullPage.min.js
988 ms
jquery.slides.min.js
988 ms
jquery.bxslider.min.js
1042 ms
jquery.isotope.js
936 ms
fake-element.js
1001 ms
cbpHorizontalMenu.min.js
1063 ms
jquery.sticky.js
1061 ms
jquery.lazyload.min.js
1062 ms
ShowObjectPicture.aspx
835 ms
ShowObjectPicture.aspx
928 ms
ShowObjectPicture.aspx
1598 ms
ShowObjectPicture.aspx
1059 ms
ShowObjectPicture.aspx
2570 ms
icon-hashie.png
1008 ms
tahoma.ttf
1095 ms
logo.PNG
841 ms
gray-bullet.png
842 ms
MjCasablanca.ttf
841 ms
slimi-section-1-right.png
742 ms
record-test.jpg
829 ms
date-icon.png
485 ms
footer-bg.JPG
569 ms
jquery.slides.min.js
477 ms
jquery.bxslider.min.js
566 ms
arrow_sub_up.gif
444 ms
arrow_sub_down.gif
444 ms
slimi-section-0.png
448 ms
slimi-section-1-left.png
624 ms
slimi-section-2.png
516 ms
slider-prev-icon.png
627 ms
slider-next-icon.png
628 ms
ShowObjectPicture.aspx
1454 ms
ShowObjectPicture.aspx
1262 ms
ShowObjectPicture.aspx
1650 ms
pec.ir 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-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
pec.ir best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
pec.ir 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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pec.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 Pec.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.
pec.ir
Open Graph description is not detected on the main page of Pec. 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: