Screenshots monitoring program performance on the server

The site is built on the Next.js framework (based on React). All points in the technical specification need to be completed. The technical specification is attached in the file. I look forward to your proposals.

Website for evaluation: https://copy.eurobrands-shop.de/ Task: fix frontend bugs at the Magento 2 / Amasty theme level: CSS/LESS/JS, mobile, RTL, minicart, language dropdown, layout shift/CLS. Work format: - without local Magento deployment; - work through DevTools + theme source files; - edits in CSS/LESS/JS/template files of the theme; - result: diff / commit / archive of changed files; - deployment and assembly on our side; - work through a secure deal; - NDA until the transfer of source files/accesses. What needs to be checked and evaluated: 1. RTL / Arabic version: - phone in the header is displayed incorrectly; - element offsets in header, minicart, wishlist/account, product page; - margins, direction, unicode-bidi, positioning. 2. Header: - language dropdown; - cart/wishlist; - hit-area of icons. 3. Minicart: - opens unstably on some pages; - check Console / Network / Event Listeners / customer-data / z-index / overlay. 4. Mobile: - cart/wishlist badges are too large; - Categories block is compressed/cut off; - mobile menu / Menu-Account. 5. Product page: - layout shift / CLS of images; - Add to Cart / Quantity / BOX / PALLET in RTL. 6. Wishlist/account: - /wishlist/ - /mwishlist/ - tabs, Back button, overflow of counters. Problematic URLs: - https://copy.eurobrands-shop.de/alpro - https://copy.eurobrands-shop.de/producers - https://copy.eurobrands-shop.de/wishlist/ - https://copy.eurobrands-shop.de/mwishlist/ In your response, please write: 1. Do you have experience with Magento 2 frontend? 2. Do you have experience with RTL? 3. How many hours do you need for the first stage? 4. What is the cost? 5. When can you start? 6. What accesses do you need? 7. Are you ready to work through a secure deal and sign an NDA? Important: a specific result is needed — corrections or a technical explanation for each point: fixed / not reproducible / not a frontend issue.

Order description: We are looking for an experienced frontend developer/OpenCart specialist to optimize the loading speed of the website (categories and product cards) according to Google Core Web Vitals requirements. About the project: * CMS: OpenCart. * Specifics: The site operates in catalog mode (no cart or checkout). * Volume: 2900 items. * Server part: Already optimized (runs on OpenLiteSpeed). * Stack: Work is done exclusively with the template code, modifiers, and frontend. No work with the database. What needs to be done (Technical task): 1. Delayed loading of scripts (Delay JS): * Problem: Third-party analytics scripts (GTM, Google Tag) block the main thread on mobile devices for about 4.3 seconds. * Task: Set up delayed execution of these scripts. The scripts should activate strictly on the first user action (first scroll, tap on the screen, or mouse movement). * Important: Data collection, analytics, and ad functionality must remain intact. 2. Fixing the CLS metric (Layout Stability): * Problem: The page "jumps" and shifts during image loading. * Task: In the style files or theme template, hardcode the HTML attributes width and height for all product images in the catalog (listings) and product cards. * Goal: Reserve space for images in the DOM tree until they are actually loaded to prevent content shifting. Ensure that responsiveness (CSS) is not broken. 3. Optimization of the critical path (LCP): * Task: Add the fetchpriority="high" tag for the main product image on the first screen. This will instruct the browser to load the main product photo as a priority. Requirements for the performer and acceptance conditions: 1. No unnecessary modules: Work is performed with clean code/modifiers, without installing additional third-party or paid optimization plugins. 2. Security and layout: You are fully responsible for the layout. After making changes, the visual display of the site on mobile and PC, as well as functionality (filters, photo switching in the gallery, menu) must remain unchanged. 3. Criteria for job submission (DoD): Provide a screenshot and a link to a live test report from Google PageSpeed Insights (for the mobile version). The performance score must be no lower than 75 points, and the CLS metric must be no more than 0.1 (in the green zone). Changes must be made strictly through modifiers (OCMOD) or a copy of the theme to avoid overwriting core updates. In your response, please indicate: 1. Have you had experience configuring Delay JS specifically for GTM on OpenCart? 2. The estimated time for task completion. 3. The cost of the work.

We will send full details in private messages Goal Maximize website loading speed, especially on mobile devices. KPI (mandatory) After the work is completed, the following metrics must be achieved. Mobile Performance 90+ LCP less than 2.2 sec INP less than 200 ms CLS less than 0.1 TBT less than 200 ms Desktop Performance 95+ What needs to be done 1. Full website audit 2. Image optimization 3. CSS 4. JavaScript 5. Caching 6. Server 7. CDN 8. WordPress 9. Database 10. Fonts 11. WooCommerce 12. Plugins 13. Core Web Vitals 14. Fix HTTPS redirect

There is a working, well-designed project on Odoo 19 Community — CRM for a Ukrainian hotel, already in production-grade infrastructure. We do not plan to rewrite from scratch. We are looking for one person who will take over the project, maintain the working state, and lead it further: first CRM → then HMS → accounting. This is a long-term collaboration, not a one-time task. Who we are looking for Senior specifically in Odoo 19 CE — inheritance-only (_inherit, _inherits, xpath), OCA-first, without core hacks, clean module boundaries. A real practitioner of Claude Code in development. Able to develop someone else's code, not reflexively rewrite it. Stack Odoo 19 Community + OCA · PostgreSQL 16 · Docker · Hetzner + Coolify · GitHub Actions CI/CD · pre-commit (ruff, pylint-odoo) · ADR in MADR · JSON-2 (not XML-RPC) · Standalone Owl when standard widgets are insufficient. AI-assisted development is the norm, not an addition. Terms of Reference: 1 task: conduct an analysis of the current state of the project 2 task: create an improvement plan 3 task: refine the CRM block and launch it into operation How to apply Describe one real project that you took over (someone else's code) and developed in production. How did you extend it without touching the core? Your Claude Code workflow in Odoo — specifically. Which OCA modules did you actually use/contribute to for v18/v19 — name them. One case where you chose Studio/config or OCA instead of custom, and one — where you correctly went for custom. DO NOT respond if You are an agency/reseller team · your first instinct is "rewrite from scratch" · Odoo only ≤ v16 or theoretical · Claude Code "I will learn as I go" · Conditions Start — paid test (small, real) → long-term collaboration Start: already The project is organized: documented architecture, ADR, CI/CD, clean git history. You inherit order, not chaos.