2 comments found.
Hi,
I noticed that the template currently includes two <header> blocks ,one with the class rs-sticky-header and another static version right below it ,apparently used to make the sticky navigation work.
This implementation creates several issues:
Invalid HTML structure (two consecutive headers for the same purpose),
Duplicate content for search engines and accessibility tools,
Layout overlap where the main banner gets partially hidden,
And unnecessary DOM duplication that affects page performance.
The sticky behavior should be managed within a single <header>, handled properly via CSS and JS.
Since this is a purchased template, I expect the final build to use a clean, valid HTML5 structure with only one header, and the sticky functionality implemented correctly without duplicating the element.
Please review and update the template accordingly so the sticky header works as intended, using best coding practices.
Thank you
Okay thanks – we will work on it and will update it. Thanks
Thanks for the update! Just let me know when you plan to apply the fix, so I can align the rest of the development and proceed with the next steps of the redesign.
I’ll pause any further changes on my side until the header is finalized.
Within Thursday thanks
Hi,
I’ve fixed the main navigation issue: the sticky header is now visible on page load, and the off-canvas menu works correctly.
Here’s what I did: I simply made the sticky header always visible and added a small script to handle the body padding dynamically.
The changes applied are:
```css #rs-sticky-header { opacity: 1 !important; visibility: visible !important; transform: none !important; } ```
<script> document.addEventListener(‘DOMContentLoaded’, function () { var header = document.getElementById(‘rs-sticky-header’); if (!header) return; function setPad(){ document.body.style.paddingTop = header.offsetHeight + ‘px’; } setPad(); window.addEventListener(‘resize’, setPad); }); </script>
However, I also noticed that the double header issue and the missing <head> opening/closing tags are present in all the pages of the template, not just on the homepage.
So you’ll need to perform a proper cleanup and update across the entire theme to ensure:
only one header is included per page,
each file has a complete and valid <head>...</head> section,
no duplicate scripts or structural conflicts remain.
Once this update is done globally, please verify and test it carefully across all pages to make sure everything behaves as expected.
Thanks for checking and updating the template accordingly, Alessio
Thanks for your effort. We are going to update today. Thanks
We already released updated version. Thanks
