26 sec in total
1.1 sec
24.8 sec
89 ms
Welcome to khaneh-mobile.ir homepage info - get ready to check Khaneh Mobile best content for Iran right away, or after learning these important things about khaneh-mobile.ir
خانه موبایل همیشه قیمتایی داره که خرید موبایل همیشه با خیال راحت انجام میدی - ارسال سریع داره که همیشه توی زمان صرفه جویی کنی - خرید موبایل
Visit khaneh-mobile.irWe analyzed Khaneh-mobile.ir page load time and found that the first response time was 1.1 sec and then it took 24.9 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.
khaneh-mobile.ir performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value6.7 s
8/100
25%
Value19.5 s
0/100
10%
Value13,110 ms
0/100
30%
Value0.469
18/100
15%
Value20.2 s
2/100
10%
1128 ms
502 ms
513 ms
531 ms
543 ms
Our browser made a total of 83 requests to load all elements on the main page. We found that 98% of them (81 requests) were addressed to the original Khaneh-mobile.ir, 1% (1 request) were made to Trustseal.enamad.ir and 1% (1 request) were made to App.raychat.io. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source Trustseal.enamad.ir.
Page size can be reduced by 719.9 kB (61%)
1.2 MB
466.5 kB
In fact, the total size of Khaneh-mobile.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. 60% of websites need less resources to load. HTML takes 710.7 kB which makes up the majority of the site volume.
Potential reduce by 665.4 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 665.4 kB or 94% of the original size.
Potential reduce by 49.0 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, Khaneh Mobile needs image optimization as it can save up to 49.0 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 5.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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 55 (74%)
74
19
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Khaneh Mobile. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
khaneh-mobile.ir
1128 ms
styles.css
502 ms
styles-rtl.css
513 ms
login.css
531 ms
main.css
543 ms
login-rtl.css
544 ms
style.css
544 ms
all.css
834 ms
elements.css
680 ms
elementor-icons.min.css
705 ms
frontend-lite-rtl.min.css
720 ms
post-17514.css
715 ms
global.css
744 ms
post-17613.css
858 ms
base.css
882 ms
header.css
889 ms
menu.css
898 ms
woocommerce-defaults.css
901 ms
general.css
998 ms
slick.css
1012 ms
footer.css
1053 ms
thf-customize-wc.min.css
1064 ms
thf-customize-wc-ajax-search.min.css
1075 ms
thf-customize-wc-modal.min.css
1078 ms
jquery.min.js
1329 ms
jquery-migrate.min.js
1176 ms
slick.min.js
1227 ms
client.js
1238 ms
thf-customize-wc.min.js
1252 ms
widget-icon-box-rtl.min.css
1256 ms
scripts.js
1245 ms
jquery.blockUI.min.js
1248 ms
add-to-cart.min.js
1248 ms
js.cookie.min.js
1248 ms
woocommerce.min.js
1248 ms
cart-fragments.min.js
1249 ms
tm-woocompare.min.js
1247 ms
tm-woowishlist.min.js
1108 ms
base.js
1099 ms
category-ajax.js
1086 ms
jquery.countdown.min.js
1082 ms
cart-qty-ajax.js
1125 ms
product.js
1151 ms
unveil.js
1079 ms
smush-lazy-load.min.js
1067 ms
pathLoader.js
1083 ms
bootstrap.tab.js
1061 ms
main.js
1091 ms
megamenu.js
1008 ms
thf-customize-wc-ajax-search.min.js
1193 ms
scrollTo.js
1170 ms
main.js
1162 ms
login.js
1154 ms
webpack.runtime.min.js
1147 ms
frontend-modules.min.js
1054 ms
waypoints.min.js
1165 ms
core.min.js
1123 ms
frontend.min.js
1114 ms
logo.aspx
20452 ms
loadingp.gif
760 ms
captcha.php
761 ms
iranyekanwebregularfanum.woff
1136 ms
iranyekanwebboldfanum.woff
1137 ms
fa-light-300.woff
1948 ms
eicons.woff
1136 ms
star.woff
919 ms
212x100_logoasli.png
221 ms
gplus-gree2n-300x300.jpg
220 ms
m5s-screen-300x300.jpg
217 ms
s22-screen-300x300.jpg
335 ms
khaneh-mobile.ir
5000 ms
admin-ajax.php
16025 ms
gplus-gallery1-300x300.jpg
175 ms
m5s-gallery2-300x300.jpg
361 ms
s22-gallery1-300x300.jpg
454 ms
honorx8xscreen-300x300.jpg
201 ms
a52-screen-300x300.jpg
374 ms
14-300x300.jpg
386 ms
62e5f903-3763-473f-ae02-baa22e4273a0
90 ms
Empty-cart.svg
167 ms
%D8%B5%D9%81%D8%AD%D9%87-%D9%86%D9%85%D8%A7%DB%8C%D8%B4-A03s-300x300.jpg
498 ms
13-300x300.jpg
495 ms
a13-screen-300x300.jpg
845 ms
khaneh-mobile.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.
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
Form elements do not have associated labels
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
khaneh-mobile.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
Page has valid source maps
khaneh-mobile.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
FA
FA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Khaneh-mobile.ir 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 Khaneh-mobile.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.
khaneh-mobile.ir
Open Graph description is not detected on the main page of Khaneh Mobile. 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: