Development of extensions for Google Chrome

Hello everyone, we need to create a website for event creation and ticket sales. Possible options include using a ready-made template, a framework, or your own solution. It is preferable that you have experience in developing websites for ticket sales. We will send examples of websites in private messages. If necessary, we will create a prototype. If you have previously worked on similar websites, please send examples in private messages. We will discuss the details in private messages. Thank you and have a great day!

What we are calculating in the project: Realized PnL, ROI, and Win Rate for cryptocurrency wallets - how profitable the wallet traded a certain token over the selected period. Based on what data: the history of on-chain transactions of the wallet (swaps, token transfers) + the market price of the token at the time of each transaction. The main data source is Moralis: two calls during the initial loading of the wallet - native ETH transfers and all ERC-20 token transfers. What we are comparing with: Nansen.io - we take it as a benchmark, comparing our calculated metrics with what Nansen shows for the same wallets over the same period. Problem: our figures significantly differ from Nansen, and we do not fully understand the rules by which some actions of the wallet should be classified for PnL purposes. We need to fix the calculation of Realized PnL, ROI, and Win Rate to match Nansen. In your application, please write: - experience with similar tasks - experience with Nansen - experience with Moralis - experience with DeFiLlama - experience with articles on crypto transactions - approximate cost and timeline for the fix

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.