5.6 sec in total
956 ms
4 sec
631 ms
Click here to check amazing Puzel content for Iran. Otherwise, check out these important facts you probably never knew about puzel.ir
مرجع فروش و قیمت موبایل،تبلت،نوت بوک
Visit puzel.irWe analyzed Puzel.ir page load time and found that the first response time was 956 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
puzel.ir performance score
name
value
score
weighting
Value8.5 s
0/100
10%
Value12.0 s
0/100
25%
Value25.4 s
0/100
10%
Value1,130 ms
23/100
30%
Value0.884
3/100
15%
Value11.4 s
19/100
10%
956 ms
313 ms
79 ms
408 ms
233 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 95% of them (87 requests) were addressed to the original Puzel.ir, 2% (2 requests) were made to Puzel.api.oneall.com and 2% (2 requests) were made to Public.oneallcdn.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Puzel.ir.
Page size can be reduced by 634.3 kB (36%)
1.7 MB
1.1 MB
In fact, the total size of Puzel.ir main page is 1.7 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. 50% of websites need less resources to load. Images take 971.9 kB which makes up the majority of the site volume.
Potential reduce by 129.5 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 19.4 kB, which is 13% 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 129.5 kB or 87% of the original size.
Potential reduce by 36.2 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. Puzel images are well optimized though.
Potential reduce by 278.8 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 278.8 kB or 72% of the original size.
Potential reduce by 189.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. Puzel.ir needs all CSS files to be minified and compressed as it can save up to 189.8 kB or 82% of the original size.
Number of requests can be reduced by 4 (5%)
87
83
The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Puzel. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for CSS and as a result speed up the page load time.
www.puzel.ir
956 ms
v_36_59ec61b249b77a2e791a32f7fead210d_all.css
313 ms
product_list.css
79 ms
v_22_522aa01e509536d7c85d584225c35517.js
408 ms
styles.css
233 ms
jquery.elevatezoom.min.js
80 ms
responsive.css
275 ms
library.js
537 ms
logo.aspx
906 ms
bg.png
515 ms
areo.png
517 ms
%D9%BE%D8%A7%D8%B2%D9%84-%D9%81%DB%8C%DA%A9%D8%B3-logo-1455142340.jpg
509 ms
3-0_thumb.jpg
512 ms
3-1_thumb.jpg
507 ms
3-2_thumb.jpg
510 ms
1.jpg
512 ms
2.jpg
513 ms
3.jpg
514 ms
4.jpg
515 ms
5.jpg
515 ms
5ed778af7be8bf69ad0e5a28984aaf4c.jpg
523 ms
3e4a9aeb1db7ef530e335fa8f3137144.gif
522 ms
6-man.jpg
516 ms
5-man.jpg
515 ms
9-man.jpg
518 ms
4-man.jpg
517 ms
1-man.jpg
757 ms
11-man.jpg
779 ms
7-man.jpg
779 ms
8-man.jpg
794 ms
10-man.jpg
802 ms
2-man.jpg
821 ms
3-man.jpg
847 ms
12-man.jpg
881 ms
1.png
947 ms
3.png
926 ms
2.png
927 ms
4.png
968 ms
8.png
974 ms
7.png
1009 ms
5.png
1039 ms
6.png
1038 ms
AAA.PNG
1100 ms
www.puzel.ir
1568 ms
10846_1491678960_1.jpg
1225 ms
fontawesome-webfont.woff
756 ms
WebYekan.woff
687 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
658 ms
cc6823dd-307f-4dad-b520-cc26b3e819f7.jpg
830 ms
icon1.png
754 ms
icon2.png
751 ms
ecolumnbnr.jpg
827 ms
%D8%A7%D9%BE%D9%84%DB%8C%DA%A9%DB%8C%D8%B4%D9%86-%D9%BE%D8%A7%D8%B2%D9%84-%D9%81%DB%8C%DA%A9%D8%B3.png
827 ms
namad%202.JPG
862 ms
%D9%82%DB%8C%D9%85%D8%AA-%DA%AF%D9%88%D8%B4%DB%8C-%D9%85%D9%88%D8%A8%D8%A7%DB%8C%D9%84-%D9%87%D9%88%D8%A7%D9%88%DB%8C-%D9%87%D9%88%D9%86%D9%88%D8%B1-3x-g750.jpg
848 ms
%D9%82%DB%8C%D9%85%D8%AA-%DA%AF%D9%88%D8%B4%DB%8C-%D9%85%D9%88%D8%A8%D8%A7%DB%8C%D9%84-%D9%87%D9%88%D8%A7%D9%88%DB%8C-%D8%A7%D8%B3%D9%86%D8%AF-y220.jpg
853 ms
%D9%82%DB%8C%D9%85%D8%AA-%DA%AF%D9%88%D8%B4%DB%8C-%D9%85%D9%88%D8%A8%D8%A7%DB%8C%D9%84-%D9%87%D9%88%D8%A7%D9%88%DB%8C-%D9%87%D9%88%D9%86%D9%88%D8%B1-3c.jpg
859 ms
%D9%82%DB%8C%D9%85%D8%AA-%DA%AF%D9%88%D8%B4%DB%8C-%D9%85%D9%88%D8%A8%D8%A7%DB%8C%D9%84-%D9%87%D9%88%D8%A7%D9%88%DB%8C-%D8%A7%D8%B3%D9%86%D8%AF-g730.jpg
863 ms
%D9%82%DB%8C%D9%85%D8%AA-%DA%AF%D9%88%D8%B4%DB%8C-%D9%85%D9%88%D8%A8%D8%A7%DB%8C%D9%84-%D9%87%D9%88%D8%A7%D9%88%DB%8C-%D9%85%D8%AF%D9%84-huawei-ascend-p7-mini.jpg
946 ms
%D9%82%DB%8C%D9%85%D8%AA-%DA%AF%D9%88%D8%B4%DB%8C-%D9%85%D9%88%D8%A8%D8%A7%DB%8C%D9%84-%D9%87%D9%88%D8%A7%D9%88%DB%8C-%D8%A7%D8%B3%D9%86%D8%AF-g6.jpg
964 ms
%DA%AF%D9%88%D8%B4%DB%8C-%D9%85%D9%88%D8%A8%D8%A7%DB%8C%D9%84-%D8%B3%D8%A7%D9%85%D8%B3%D9%88%D9%86%DA%AF-%D9%85%D8%AF%D9%84-samsung-galaxy-j1-2016-sm-j120.jpg
1009 ms
%DA%AF%D9%88%D8%B4%DB%8C-%D9%85%D9%88%D8%A8%D8%A7%DB%8C%D9%84-%D8%B3%D8%A7%D9%85%D8%B3%D9%88%D9%86%DA%AF-%D9%85%D8%AF%D9%84-samsung-galaxy-a9-2016-sm-a910.jpg
969 ms
125 ms
beveled_w35_h35_wc_v1.css
56 ms
beveled_w35_h35_c_v1.png
56 ms
%DA%AF%D9%88%D8%B4%DB%8C-%D9%85%D9%88%D8%A8%D8%A7%DB%8C%D9%84-%D8%B3%D8%A7%D9%85%D8%B3%D9%88%D9%86%DA%AF-%D9%85%D8%AF%D9%84-samsung-galaxy-a7-2016-sm-a710.jpg
755 ms
%DA%AF%D9%88%D8%B4%DB%8C-%D9%85%D9%88%D8%A8%D8%A7%DB%8C%D9%84-%D8%B3%D8%A7%D9%85%D8%B3%D9%88%D9%86%DA%AF-%D9%85%D8%AF%D9%84-samsung-galaxy-a5-2016-sm-a510.jpg
941 ms
%D9%82%DB%8C%D9%85%D8%AA-%DA%AF%D9%88%D8%B4%DB%8C-%D9%85%D9%88%D8%A8%D8%A7%DB%8C%D9%84-%D8%A7%DA%86-%D8%AA%DB%8C-%D8%B3%DB%8C-%D9%88%D8%A7%D9%86-m9-%D9%BE%D9%84%D8%A7%D8%B3.jpg
1026 ms
bahman1.png
913 ms
bahman2.png
905 ms
bahman3.png
930 ms
bahman4.png
870 ms
1.png
901 ms
2.png
853 ms
3.png
885 ms
sep.png
864 ms
icon_top.png
864 ms
themes.png
885 ms
delete.gif
1021 ms
star.gif
857 ms
%D9%82%DB%8C%D9%85%D8%AA-%DA%AF%D9%88%D8%B4%DB%8C-%D9%85%D9%88%D8%A8%D8%A7%DB%8C%D9%84-%D8%B3%D8%A7%D9%85%D8%B3%D9%88%D9%86%DA%AF-%DA%AF%D9%84%DA%A9%D8%B3%DB%8C-a8.jpg
856 ms
motorola-moto-x-2013.jpg
809 ms
motorola-moto-g-3rd-gen.jpg
739 ms
AjaxLoader.gif
683 ms
%D9%82%DB%8C%D9%85%D8%AA-%DA%AF%D9%88%D8%B4%DB%8C-%D9%85%D9%88%D8%A8%D8%A7%DB%8C%D9%84-%D9%87%D9%88%D8%A7%D9%88%DB%8C-%D9%87%D9%88%D9%86%D9%88%D8%B1-3x-g750.jpg
719 ms
%D9%82%DB%8C%D9%85%D8%AA-%DA%AF%D9%88%D8%B4%DB%8C-%D9%85%D9%88%D8%A8%D8%A7%DB%8C%D9%84-%D9%87%D9%88%D8%A7%D9%88%DB%8C-%D8%A7%D8%B3%D9%86%D8%AF-y220.jpg
719 ms
%D9%82%DB%8C%D9%85%D8%AA-%DA%AF%D9%88%D8%B4%DB%8C-%D9%85%D9%88%D8%A8%D8%A7%DB%8C%D9%84-%D9%87%D9%88%D8%A7%D9%88%DB%8C-%D9%87%D9%88%D9%86%D9%88%D8%B1-3c.jpg
854 ms
%D9%82%DB%8C%D9%85%D8%AA-%DA%AF%D9%88%D8%B4%DB%8C-%D9%85%D9%88%D8%A8%D8%A7%DB%8C%D9%84-%D9%87%D9%88%D8%A7%D9%88%DB%8C-%D8%A7%D8%B3%D9%86%D8%AF-g730.jpg
802 ms
%DA%AF%D9%88%D8%B4%DB%8C-%D9%85%D9%88%D8%A8%D8%A7%DB%8C%D9%84-%D8%B3%D8%A7%D9%85%D8%B3%D9%88%D9%86%DA%AF-%D9%85%D8%AF%D9%84-samsung-galaxy-j1-2016-sm-j120.jpg
817 ms
%DA%AF%D9%88%D8%B4%DB%8C-%D9%85%D9%88%D8%A8%D8%A7%DB%8C%D9%84-%D8%B3%D8%A7%D9%85%D8%B3%D9%88%D9%86%DA%AF-%D9%85%D8%AF%D9%84-samsung-galaxy-a9-2016-sm-a910.jpg
792 ms
%DA%AF%D9%88%D8%B4%DB%8C-%D9%85%D9%88%D8%A8%D8%A7%DB%8C%D9%84-%D8%B3%D8%A7%D9%85%D8%B3%D9%88%D9%86%DA%AF-%D9%85%D8%AF%D9%84-samsung-galaxy-a7-2016-sm-a710.jpg
830 ms
%DA%AF%D9%88%D8%B4%DB%8C-%D9%85%D9%88%D8%A8%D8%A7%DB%8C%D9%84-%D8%B3%D8%A7%D9%85%D8%B3%D9%88%D9%86%DA%AF-%D9%85%D8%AF%D9%84-samsung-galaxy-a5-2016-sm-a510.jpg
823 ms
puzel.ir accessibility score
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
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.
puzel.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
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
puzel.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
EN
FA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Puzel.ir can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Persian language. Our system also found out that Puzel.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.
puzel.ir
Open Graph description is not detected on the main page of Puzel. 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: