6 sec in total
459 ms
5.1 sec
433 ms
Welcome to eshore.in homepage info - get ready to check EShore best content right away, or after learning these important things about eshore.in
Limil eShore, buy with confidence
Visit eshore.inWe analyzed Eshore.in page load time and found that the first response time was 459 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
eshore.in performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value5.1 s
25/100
25%
Value6.3 s
41/100
10%
Value40 ms
100/100
30%
Value0.201
62/100
15%
Value5.1 s
75/100
10%
459 ms
952 ms
446 ms
648 ms
817 ms
Our browser made a total of 97 requests to load all elements on the main page. We found that 98% of them (95 requests) were addressed to the original Eshore.in, 1% (1 request) were made to Fonts.googleapis.com and 1% (1 request) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Eshore.in.
Page size can be reduced by 131.4 kB (12%)
1.1 MB
928.7 kB
In fact, the total size of Eshore.in main page is 1.1 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. 40% of websites need less resources to load. Images take 883.1 kB which makes up the majority of the site volume.
Potential reduce by 66.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. 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 66.5 kB or 90% of the original size.
Potential reduce by 63.1 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. EShore images are well optimized though.
Potential reduce by 968 B
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.
Potential reduce by 754 B
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. Eshore.in has all CSS files already compressed.
Number of requests can be reduced by 10 (21%)
47
37
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EShore. 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 from 7 to 1 for CSS and as a result speed up the page load time.
eshore.in
459 ms
eshore.in
952 ms
jquery-2.1.1.min.js
446 ms
bootstrap.min.css
648 ms
bootstrap.min.js
817 ms
font-awesome.min.css
814 ms
stylesheet.min.css
821 ms
swiper.min.css
836 ms
opencart.css
847 ms
swiper.jquery.min.js
848 ms
common.js
998 ms
live_search.css
999 ms
live_search.js
1008 ms
jquery-2.1.1.min.js
957 ms
bootstrap.min.css
969 ms
font-awesome.min.css
608 ms
bootstrap.min.js
620 ms
stylesheet.min.css
763 ms
swiper.min.css
753 ms
opencart.css
783 ms
swiper.jquery.min.js
995 ms
common.js
636 ms
live_search.css
774 ms
live_search.js
767 ms
css
34 ms
logo_final.png
203 ms
maharaja-250x200.png
196 ms
samsung_16gb_sdcard-250x200.jpg
203 ms
Radio2-250x200.jpg
187 ms
gprs-oled-tvs-1140x380.jpg
190 ms
gprs-smart-tvs-1140x380.png
187 ms
Banner%20Pay%20Modes-1140x380.jpg
375 ms
gprs_ultra_hd-1140x380.jpg
374 ms
fhd-smart-40-inch-200x200.jpg
379 ms
bta_1-200x200.gif
390 ms
smart_fhd_40_inch-200x200.jpeg
403 ms
maharaja_joy_elite_1-200x200.jpg
405 ms
microdata_sd_card_1-200x200.jpg
559 ms
sherawali_2g-200x200.png
560 ms
LED_24%20Inch-200x200.jpg
567 ms
mr_inspira_1-200x200.png
584 ms
tab_1-200x200.jpg
604 ms
baby_saffron_1g-200x200.png
607 ms
redmi_note_10_128GB_6GB-200x200.jpg
744 ms
realme_c20_grey_1-200x200.png
744 ms
module_1-200x200.png
754 ms
bajaj_dx7_light_1-200x200.png
778 ms
lenovo_laptop_1-200x200.jpeg
806 ms
lg_49UJ632t_1-200x200.png
809 ms
limil_water_alarm-200x200.png
928 ms
dell-130x100.png
929 ms
3m-130x100.png
945 ms
lenovo-130x100.png
971 ms
lg-130x100.png
1008 ms
samsung-130x100.png
1011 ms
sandisk-130x100.png
1112 ms
sony-130x100.png
1114 ms
canon-130x100.png
1133 ms
samsung_16gb_sdcard-200x200.jpg
1166 ms
micromax_1-200x200.jpg
1210 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf
52 ms
fontawesome-webfont.woff
561 ms
Radio2-250x200.jpg
193 ms
gprs-smart-tvs-1140x380.png
814 ms
gprs-oled-tvs-1140x380.jpg
379 ms
maharaja-250x200.png
393 ms
logo_final.png
400 ms
samsung_16gb_sdcard-250x200.jpg
369 ms
gprs_ultra_hd-1140x380.jpg
575 ms
Banner%20Pay%20Modes-1140x380.jpg
770 ms
fhd-smart-40-inch-200x200.jpg
408 ms
bta_1-200x200.gif
412 ms
smart_fhd_40_inch-200x200.jpeg
394 ms
maharaja_joy_elite_1-200x200.jpg
578 ms
microdata_sd_card_1-200x200.jpg
426 ms
sherawali_2g-200x200.png
441 ms
LED_24%20Inch-200x200.jpg
571 ms
mr_inspira_1-200x200.png
606 ms
tab_1-200x200.jpg
569 ms
baby_saffron_1g-200x200.png
596 ms
redmi_note_10_128GB_6GB-200x200.jpg
457 ms
realme_c20_grey_1-200x200.png
584 ms
module_1-200x200.png
583 ms
bajaj_dx7_light_1-200x200.png
582 ms
lenovo_laptop_1-200x200.jpeg
581 ms
lg_49UJ632t_1-200x200.png
591 ms
limil_water_alarm-200x200.png
479 ms
dell-130x100.png
597 ms
3m-130x100.png
583 ms
lenovo-130x100.png
575 ms
lg-130x100.png
578 ms
samsung-130x100.png
588 ms
sandisk-130x100.png
496 ms
sony-130x100.png
600 ms
canon-130x100.png
586 ms
samsung_16gb_sdcard-200x200.jpg
568 ms
micromax_1-200x200.jpg
574 ms
eshore.in 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
Links do not have a discernible name
eshore.in 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
Browser errors were logged to the console
Page has valid source maps
eshore.in SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
![]()
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eshore.in can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Eshore.in 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.
eshore.in
Open Graph description is not detected on the main page of EShore. 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: