Auditing the site for errors

Description: It is necessary to accurately layout two pages of an analytical interface according to the ready-made design from Figma (exactly one to one) Link: https://www.figma.com Scope of work: Single Location Page: metric cards, two pie charts, leaderboard table. Multi-Location Page: cards, interactive map of the USA (by states), performance table. Requirements: Stack: Any at your discretion (HTML/CSS/JS, Tailwind, React, Vue, etc.) — we will do the final code conversion for our needs ourselves. Quality: Strictly 1 to 1, neat responsive grid. In your response, please specify your stack, price, realistic deadlines, and attach 1–2 examples of admin panels or dashboards you have laid out.

# Need a Frontend Developer (WordPress / WooCommerce): Product Card ## About the Project Active online store The design is already ready — need to be properly coded and integrated product card (single product). - Current page (example): https://obertshop.com.ua/shop/dysky/audi/r21-audi/disk-r21-na-avto-audi-obr9006/ Template coding for single-product ## Requirements - Coding according to the Figma layout. - Responsive: desktop + mobile, correct display in major browsers. - Integration into the existing WooCommerce theme, clean and maintainable code. - Result — a working page on the site that matches the design. ## What to Send in Your Response 1. Portfolio (preferably WordPress / WooCommerce, product cards). 2. Cost — suggest a convenient format (fixed price for the project or hourly rate). 3. Deadline in days. 4. Questions about the layout and a list of accesses/materials needed from us to start. Access to Figma, the site, and necessary materials will be provided in private messages after the response.

A website needs to be coded according to the design. The layout is a bit crooked, so pixel perfect is not required. Coding, responsive for mobile devices, opening pages via links, and the site in three languages. All texts in blocks in other languages will be sent later. Additionally: optimization for Google PageSpeed 100 / 100 for mobile and desktop. Or at least 98 out of 100, no less!!! Propose timelines and costs. Layout: https://www.figma.com/design/AkM2GAvaLAPw7IAOtkGPIy/DSL-2010--%D0%9F%D1%80%D0%B0%D0%B2%D0%BA%D0%B8-1-?node-id=6177-908&t=u7qPBPqxIifkwaug-0

The website is developed on: Backend: Java + Spring Boot Database: MySQL Frontend: JavaScript, HTML, CSS Template Engine: Thymeleaf Server: VPS (Linux Ubuntu) Reverse Proxy: Apache2 Architecture: Monolithic application Currently, the website has implemented: A blog with an admin panel. The ability to create and edit articles through the admin panel. The ability to add HTML markup and content through a visual interface. Static pages of the site, which are currently created by the developer manually. ⸻ Task Objective It is necessary to implement the ability to create and manage new commercial service pages through the existing admin panel similarly to how blog articles are currently created. After implementation, the administrator should be able to independently create new SEO service pages without the involvement of the developer. ⸻ Current State Currently, only blog posts can be created through the admin panel. Example: Article 1 Article 2 Article 3 Each article has: Title URL (slug) Content SEO parameters Images ⸻ What Needs to be Implemented 1. New content type "Services" Create a separate section in the admin panel: "Services" It should be independent of the blog section. Example structure: Blog Services ⸻ 1. Creating a service page The administrator should be able to create a new service page through the interface. Commercial service pages consist of 13 blocks, of which 4 blocks are dynamic and 9 are static. Fields: Service name URL (slug) H1 SEO Title Meta Description SEO Keywords Main content of the page Image Publication status (Draft / Published) ⸻ 1. Page content The content should support: HTML markup Text formatting Headings H2-H6 Lists Images Links It is preferable to use the existing editor that is already applied in the blog. ⸻ 1. URL generation Each service should have its own URL. Examples: /visa/usa/business-visa-usa /visa/usa/business-visa-uk /visa/usa/business-visa-canada ⸻ 1. Display on the site After publication, the page should: automatically become available at its URL; use the existing service page template or a new template; display correctly on all devices. ⸻ 1. SEO For each service, it is necessary to provide the ability to configure: Title Description H1 Canonical URL (preferably) Open Graph (preferably) Pages should be indexed by search engines similarly to blog pages. ⸻ 1. List of services In the admin panel, implement: a list of all services; search; editing; deletion; changing publication status. ⸻ 1. Important Implement the ability to create new types of SEO pages without code modifications in the future. through a unified content management mechanism. ⸻ What is Expected from the Developer It is necessary to analyze the existing implementation of the blog and maximize the reuse of the current architecture to create the new "Services" section. When responding, please indicate: How the task will be implemented. What changes will be required in the database. Time estimate. Cost of work. What technologies should the performer know Mandatory: Java Spring Boot MySQL Thymeleaf HTML/CSS JavaScript Working with Linux Ubuntu Desirable: Spring Security SEO optimization of server pages Experience with CMS and CRUD modules Experience supporting monolithic Spring Boot projects

It is necessary to conduct an audit of the existing website, fix technical errors, improve SEO, optimize speed, and gradually enhance functionality. Redesign is not required. What needs to be done: Conduct a technical audit of the website. Conduct an SEO audit and propose a plan for improvements. Identify and eliminate technical errors. Propose improvements for UX/UI and design. Optimize loading speed. Make enhancements to the website, and if necessary, work with the code. In the future — support and development of the website. In your response, please include: links to similar projects; experience working with WordPress (if any); estimated cost of work; whether you are ready for long-term cooperation.