- Posts: 1184
- Thank you received: 13
Product listing quantity input notice
5 years 2 months ago #334399
by verzevoul
Product listing quantity input notice was created by verzevoul
-- HikaShop version -- : 4.4.3
-- Joomla version -- : 3.9.28
Hi!
I noticed that the quantity input at products listing causes a notice (see screenshot).
I'm not sure what it is. My website is pretty slow though and i was wonndering if it has something to do with it.
Thank you
-- Joomla version -- : 3.9.28
Hi!
I noticed that the quantity input at products listing causes a notice (see screenshot).
I'm not sure what it is. My website is pretty slow though and i was wonndering if it has something to do with it.
Thank you
Please Log in or Create an account to join the conversation.
5 years 2 months ago #334404
by nicolas
Replied by nicolas on topic Product listing quantity input notice
Hi,
You should not worry about these.
The duplicate ids come from the owl carousel system which duplicates the quantity input fields when creating clones of the products for the carousel system:
stackoverflow.com/questions/33119078/clo...tems-in-owl-carousel
While it's possible to avoid these warnings by turning off the looping of the carousel, it would solve anything:
- your carousel will be less smooth
- search engines still won't see duplicate elements as the raw HTML of the page doesn't have the clone elements for the smooth looping of the carousel
- it won't change anything for the speed of display of the page.
If you look at the "network" tab of the developer tool of your browser when looking at your pages, you'll see that most of the time spent displaying a page is spent waiting for the server to generate the HTML. To know exactly where it comes from, you need to activate the "debug" of the Joomla configuration and look at the bottom of the pages on your frontend. You'll get a break down of the different steps generating the page so you'll be able to better understand where the bottleneck is.
Also, while looking at your page, I noticed something strange:
i.imgur.com/sLWPvIj.png
On the 8 seconds it takes to display the page, while 3.8 seconds (the green area) is taken for the page generation, you have the first 3 seconds which are spent with your server redirecting from www.yourwebsite.gr/ to www.yourwebsite.gr/ and then back to www.yourwebsite.gr/
So you might have an issue at the web server level (the httpd.conf or the htaccess) which creates that 3 second redirect delay. If you could remove that problem you would save 40% of the total time spent, saving a lot of time.
You should not worry about these.
The duplicate ids come from the owl carousel system which duplicates the quantity input fields when creating clones of the products for the carousel system:
stackoverflow.com/questions/33119078/clo...tems-in-owl-carousel
While it's possible to avoid these warnings by turning off the looping of the carousel, it would solve anything:
- your carousel will be less smooth
- search engines still won't see duplicate elements as the raw HTML of the page doesn't have the clone elements for the smooth looping of the carousel
- it won't change anything for the speed of display of the page.
If you look at the "network" tab of the developer tool of your browser when looking at your pages, you'll see that most of the time spent displaying a page is spent waiting for the server to generate the HTML. To know exactly where it comes from, you need to activate the "debug" of the Joomla configuration and look at the bottom of the pages on your frontend. You'll get a break down of the different steps generating the page so you'll be able to better understand where the bottleneck is.
Also, while looking at your page, I noticed something strange:
i.imgur.com/sLWPvIj.png
On the 8 seconds it takes to display the page, while 3.8 seconds (the green area) is taken for the page generation, you have the first 3 seconds which are spent with your server redirecting from www.yourwebsite.gr/ to www.yourwebsite.gr/ and then back to www.yourwebsite.gr/
So you might have an issue at the web server level (the httpd.conf or the htaccess) which creates that 3 second redirect delay. If you could remove that problem you would save 40% of the total time spent, saving a lot of time.
The following user(s) said Thank You: verzevoul
Please Log in or Create an account to join the conversation.
Time to create page: 0.152 seconds