26.3 sec in total
1.5 sec
24.4 sec
439 ms
Visit slicer.ir now to see the best up-to-date Slicer content for Iran and also check out these interesting facts you probably never knew about slicer.ir
کالباس بر و اسلایسر صنعتی جهت اسلایس انواع مواد غذایی به کار می رود ، دستگاه اسلایسر و چرخ گوشت بهترین روش جهت اسلایس است که در هنگام برش ، مواد غذایی را خرد و ظاهر آنها را از بین نمی برد ، خرید کالبا...
Visit slicer.irWe analyzed Slicer.ir page load time and found that the first response time was 1.5 sec and then it took 24.8 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.
slicer.ir performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value8.2 s
2/100
25%
Value11.8 s
4/100
10%
Value4,710 ms
0/100
30%
Value0.096
90/100
15%
Value11.9 s
17/100
10%
1453 ms
881 ms
1269 ms
422 ms
245 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 97% of them (68 requests) were addressed to the original Slicer.ir, 1% (1 request) were made to Trustseal.enamad.ir and 1% (1 request) were made to Enamad.ir. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source Enamad.ir.
Page size can be reduced by 382.6 kB (26%)
1.5 MB
1.1 MB
In fact, the total size of Slicer.ir main page is 1.5 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. 20% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 86.7 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 20.3 kB, which is 20% 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 86.7 kB or 86% of the original size.
Potential reduce by 78.9 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. Slicer images are well optimized though.
Potential reduce by 138.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 138.4 kB or 77% of the original size.
Potential reduce by 78.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. Slicer.ir needs all CSS files to be minified and compressed as it can save up to 78.6 kB or 88% of the original size.
Number of requests can be reduced by 21 (31%)
67
46
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Slicer. 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 JavaScripts and as a result speed up the page load time.
slicer.ir
1453 ms
UserSheetFa.css
881 ms
jquery-1.7.2.min.js
1269 ms
jquery.hoverIntent.minified.js
422 ms
fmslideshow.css
245 ms
fmslideshow.min.js
418 ms
typed.js
607 ms
jquery.dctooltip.1.0.js
411 ms
Style.css
454 ms
logo.aspx
1005 ms
Picuserlogin.png
226 ms
Picuserregister.png
212 ms
arrowDown.png
222 ms
Basketcontainer.png
221 ms
ImageAutoCapmlet.png
230 ms
%DA%A9%D8%A7%D9%84%D8%A8%D8%A7%D8%B3-%D8%A8%D8%B1.png
236 ms
%DA%A9%D8%A7%D9%84%D8%A8%D8%A7%D8%B3-%D8%A8%D8%B1-%D8%AF%D8%B3%D8%AA%DB%8C.jpg
463 ms
aaaaaa%DA%A9%D8%A7%D9%84%D8%A8%D8%A7%D8%B3-%D8%A8%D8%B1-%D8%A7%D8%AA%D9%88%D9%85%D8%A7%D8%AA%DB%8C%DA%A9.jpg
439 ms
aaaaa%DA%A9%D8%A7%D9%84%D8%A8%D8%A7%D8%B3-%D8%A8%D8%B1-%D8%A7%D8%AA%D9%88%D9%85%D8%A7%D8%AA%DB%8C%DA%A9.jpg
1040 ms
%D8%A7%D8%B3%D9%84%D8%A7%DB%8C%D8%B3%D8%B1.png
459 ms
a%D8%A7%D8%B3%D9%84%D8%A7%DB%8C%D8%B3%D8%B1-%D8%B5%D9%86%D8%B9%D8%AA%DB%8C.jpg
866 ms
%D8%AE%D9%84%D8%A7%D9%84-%DA%A9%D9%86.jpg
482 ms
a%D8%AE%D9%84%D8%A7%D9%84-%DA%A9%D9%86.jpg
652 ms
%D8%B3%D8%A8%D8%B2%DB%8C-%D8%AE%D8%B1%D8%AF-%DA%A9%D9%86.jpg
670 ms
%DA%86%D8%B1%D8%AE-%DA%AF%D9%88%D8%B4%D8%AA.png
674 ms
%DA%86%D8%B1%D8%AE-%DA%AF%D9%88%D8%B4%D8%AA-%D8%B5%D9%86%D8%B9%D8%AA%DB%8C.png
1117 ms
%DA%86%D8%B1%D8%AE-%DA%AF%D9%88%D8%B4%D8%AA-%D8%B5%D9%86%D8%B9%D8%AA%DB%8C-%D8%A7%D9%85%DA%AF%D8%A7.jpg
881 ms
a%D8%AF%D8%B3%D8%AA%DA%AF%D8%A7%D9%87-%DA%A9%D8%A7%D9%84%D8%A8%D8%A7%D8%B3-%D8%A8%D8%B1.png
1337 ms
%DA%A9%D8%A7%D9%84%D8%A8%D8%A7%D8%B3-%D8%A8%D8%B1-1.png
1302 ms
%DA%A9%D8%A7%D9%84%D8%A8%D8%A7%D8%B3-%D8%A8%D8%B1-%D8%AA%D8%B1%D8%A7%D8%B2%D9%88-%D8%AF%D8%A7%D8%B1-%D9%85%D8%AD%DA%A9-%D8%B3%D8%A7%DB%8C%D8%B2-275.jpg
1082 ms
%DA%A9%D8%A7%D9%84%D8%A8%D8%A7%D8%B3-%D8%A8%D8%B1-%D9%BE%D8%A7%D8%B1%D8%B3-%D8%A8%D8%B1%D8%B4-%D8%B3%D8%A7%DB%8C%D8%B2-275.jpg
1098 ms
%DA%A9%D8%A7%D9%84%D8%A8%D8%A7%D8%B3-%D8%A8%D8%B1-%D8%A7%DB%8C%D8%AA%D8%A7%D9%84%DB%8C%D8%A7%DB%8C%DB%8C-%D8%A7%D8%AA%D9%88%D9%85%D8%A7%D8%AA%DB%8C%DA%A9-OMEGA-%D9%85%D8%AF%D9%84-BF300%D9%88BF350.jpg
1462 ms
%DA%A9%D8%A7%D9%84%D8%A8%D8%A7%D8%B3-%D8%A8%D8%B1-%D8%A8%D8%B1%D8%A7%DA%A9%D8%B3-%D8%A7%D8%AA%D9%88%D9%85%D8%A7%D8%AA%DB%8C%DA%A9-bm320.jpg
1294 ms
%DA%A9%D8%A7%D9%84%D8%A8%D8%A7%D8%B3-%D8%A8%D8%B1-%D9%85%D8%AD%DA%A9-%D8%B3%D8%A7%DB%8C%D8%B2-275.jpg
1344 ms
SmartPicture.aspx
1352 ms
Available-badge.png
1494 ms
SmartPicture.aspx
1517 ms
SmartPicture.aspx
1529 ms
SmartPicture.aspx
1532 ms
SmartPicture.aspx
1544 ms
Header.png
1647 ms
navSep.png
1678 ms
Yekan.woff
1706 ms
Search1.png
1711 ms
toggle_down_light.png
1764 ms
Logo.png
1751 ms
eNamadLogo.htm
1645 ms
WatchList_Select
2070 ms
WatchList_SelectCount
2168 ms
borderNav.png
1722 ms
2.png
1744 ms
0.png
1754 ms
3.png
1654 ms
HeadeBottom.png
1687 ms
ico-1.png
1740 ms
ico-2.png
1720 ms
ico-3.png
1640 ms
ico-4.png
1734 ms
ico-5.png
1734 ms
BoxBottom1.png
1534 ms
verticalseparator.png
1605 ms
footer.png
1452 ms
borderFooter.png
1503 ms
LogoFooter.png
1509 ms
social-icons.png
1501 ms
loader_img.png
1326 ms
tooltip.png
1397 ms
slider-arrow1.png
1376 ms
symbol.aspx
20354 ms
sprite.png
202 ms
slicer.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
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
slicer.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
slicer.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
FA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Slicer.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 Slicer.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.
slicer.ir
Open Graph description is not detected on the main page of Slicer. 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: