How to use this page:
Find your selected Jira issues in the table below. Select the expand to use them as your source of truth to write release notes.
|
Release |
https://cheitgroup.atlassian.net/projects/SCLB/versions/10356 |
|
Date |
|
|
Version |
19.11 – Release 2.21.3 |
|
Description |
|
|
Contributors |
General info
This story focuses on improving the user interface and usability of the registration window on saclab.com/sell (step 3). The changes include the display of clear password rules when a user interacts with the password input field and adjusting the spacing and margins of the form according to the new design guidelines.
As a user,
I want to see clear password rules and improved spacing in the registration window
So that I can easily create an account with the correct password requirements and a better user interface.
|
Acceptance criteria |
||
|---|---|---|
|
01 |
Scenario: Display password rules on the register window Given: I am on step 3 of the SYB and registering to continue submitting my bag When I am on the registration window Then I should see a list of password rules that include (similar to when the user wants to change password): 
AND all password interaction should follow the rules as outlined in the "Story 10.1.2. My account settings Redesign" document available at: Story 10.1.2. My account settings Redesign |
Figma: Desk: https://www.figma.com/design/6KT0tZfJw3u7R8b5pCH8vw/Saclab-Team-Library?node-id=8495-8620&m=dev Mobile: https://www.figma.com/design/6KT0tZfJw3u7R8b5pCH8vw/Saclab-Team-Library?node-id=8503-20924&m=dev |
|
02 |
Scenario: Adjust spacing and margin in the SYB register window (step 3) so it fits with the new 4-grid rule When I am on step 3 of the SYB and registering to continue submitting my bag Then the spacing between form fields should follow the updated design guidelines And the margins of the page should follow the updated design guidelines |
General info
This task focuses on optimizing web vitals across multiple sections of the site, with an emphasis on improving LCP and reducing loading times for critical resources. Investigations revealed that simultaneous loading of images and render-blocking resources are the main bottlenecks. Specific adjustments will be applied to product pages, homepage, and the product feed on both mobile and desktop devices. The goal is to pass all Core Web Vitals in future reports.
Please investigate the reports below and evaluate our suggested changes in the acceptance criteria. Let us know if you do not recommend certain changes or do not see their value. Let us know about other possible solutions you have in mind.
As Saclab, we want to optimize the loading performance and web vitals of critical pages to ensure faster page rendering and improved user experience across all devices.
Product Page Report (Mobile): https://pagespeed.web.dev/analysis/https-saclab-com-bags-hermes-halzan-mini-swift-rouge-grenat/nuiddgwnl6?form_factor=mobile
Product Page Report (Desktop): https://pagespeed.web.dev/analysis/https-saclab-com-bags-hermes-halzan-mini-swift-rouge-grenat/nuiddgwnl6?form_factor=desktop
Homepage Report (Mobile): https://pagespeed.web.dev/analysis/https-saclab-com/5qo0jw7pq4?form_factor=mobile
Homepage Report (Desktop): https://pagespeed.web.dev/analysis/https-saclab-com/5qo0jw7pq4?form_factor=desktop
Product Feed Report (Mobile): https://pagespeed.web.dev/analysis/https-saclab-com-bags/wmy5s156n2?form_factor=mobile
Product Feed Report (Desktop): https://pagespeed.web.dev/analysis/https-saclab-com-bags/wmy5s156n2?form_factor=desktop
Acceptance criteria |
||
|---|---|---|
|
01.0 |
Product Pages |
|
|
01.1 |
Product Pages Desktop and Mobile AR: Core Web Vitals FAILED, but when I test desktop locally, performance seems good Given 28 day collection period shows failed core web vitals |
|
|
01.2 |
Product Pages Mobile AR: all images load simultaneously When the page starts loading |
|
|
01.3 |
Product Pages Mobile AR: web.dev insights indicates unused CSS and render-blocking resources |
|
|
01.4 |
Product Pages Desktop Given critical resources block rendering |
|
|
02.0 |
Homepage saclab.com |
|
|
02.1 |
Homepage Desktop and Mobile AR: Homepage Core Web Vitals FAILED. Desktop performance is acceptable during local testing, but the mobile version has poor LCP and FCP Given the 28-day collection period shows failed core web vitals |
 
|
|
02.2 |
Homepage Mobile AR: The top header image impacts LCP, making the entire page count as LCP. When the page loads Then prioritize the top header image for loading and ensure LCP is below 2.5 seconds |
|
|
02.3 |
Homepage Mobile Given critical resources block rendering |
 
|
|
03.0 |
Product Feed |
|
|
03.1 |
Product Feed Desktop and Mobile AR: Product Feed Core Web Vitals FAILED. Performance is poor due to image sizes, lazy-loading issues, and swipe functionality on mobile. Given the 28-day collection period shows failed core web vitals |
|
|
03.2 |
Product Feed Desktop AR: Recent poor performance might be due to server issues. Given product feed desktop has poor Core Web Vitals And if performance improvement is needed: Then use plugin to compress hover images witouth significant loss of quality |
|
|
03.3 |
Product Feed Mobile AR: Poor performance, various Diagnostics to improve performance Given performance issues |
|
|
03.4 |
Product Feed Mobile: Suggestion AR: Swipe functionality loads all product images at once AND it actually loads all images. Given swipe functionality is active |
|
|
03.5 |
Product Feed Mobile: Suggestion AR: Image sizes are too large for mobile performance. Given product images are large |
|
|
03.6 |
Product Feed Mobile: Suggestion AR: Too many products are loaded simultaneously, causing delays. Given too many products are loaded |
|
|
03.7 |
Product Feed Mobile: Suggestion AR: LCP score is low Given the LCP is set as the Heading Title When the product feed starts loading Then load H1 sooner to get a better LCP score |
|
Improving Core Web Vitals is critical to enhance site performance, user experience, and SEO rankings. This Epic addresses identified bottlenecks, including LCP, FCP, and TTFB issues, across key sections of the website (Homepage, Product Pages, Product Feed).
Epic ticket:
As a user, I want product pages to load quickly so I can see the products I’m interested in without delays.
Address simultaneous image loading to prioritize visible content (LCP).
Minimize render-blocking resources to ensure faster FCP.
As a user, I want the homepage to feel responsive so I can access key information immediately.
Optimize top header image loading for mobile to reduce LCP times.
Eliminate render-blocking CSS and JS to speed up initial rendering.
As a user, I want to browse products efficiently without waiting for unnecessary elements to load.
Reduce image sizes and implement lazy-loading for hidden product feed images.
Limit swipeable product images to the first three for faster interactions.
Desktop:
No design changes are planned for Desktop as current layouts are functional. Focus is on technical performance improvements.
Mobile:
Ensure that technical improvements align with existing mobile-friendly layouts and do not affect usability or responsiveness.
How to use this page
The release notes on this page have been generated using the Jira issues macro. Each column of the table represents one of the issue fields you selected to include when you created these release notes in Jira.
To edit any of these fields:
Select Edit or type e to edit this Confluence page.
Select the Jira issues macro table and then select the edit icon.
Select Display options to adjust the columns and number of issues that will appear in your table of issues.
Select Insert to save your changes.
How to use this page
The release notes on this page have been generated using the Jira issues macro. Each column of the table represents one of the issue fields you selected to include when you created these release notes in Jira.
To edit any of these fields:
Select Edit or type e to edit this Confluence page.
Select the Jira issues macro table and then select the edit icon.
Select Display options to adjust the columns and number of issues that will appear in your table of issues.
Select Insert to save your changes.
Objective: Modify breadcrumb labels for improved navigation and SEO consistency site-wide and on specific pages.
Replace “Home” with “Saclàb” across all breadcrumbs site-wide.
Replace “Shop Authentic Pre-owned Designer Handbags” with “Shop Designer Handbags” across all breadcrumbs site-wide.
Structure: Saclàb > Shop Designer Handbags > Brand Name
Example: On a /brands/chanel page, the breadcrumb should read:Saclàb > Shop Designer Handbags > Chanel
Ensure uniformity across all instances of breadcrumbs.
Test each breadcrumb variation to confirm correct navigation paths and label accuracy.
|
1 |
Scenario 1: Update site-wide breadcrumb labels Given: I am on any page of the website When: I view the breadcrumb Then "Home" should be replaced with "Saclàb" And "Shop Authentic Pre-owned Designer Handbags" should be replaced with "Shop Designer Handbags" And the breadcrumb should include BreadcrumbList structured data |
|
2 |
Scenario 2: Verify structured data implementation for BreadcrumbList Given I am on any page with a breadcrumb When I inspect the page source Then the breadcrumb should contain structured data in JSON-LD format for BreadcrumbList And each item should include "@type": "ListItem" with "position" and "name" attributes And "item" should contain the URL of each breadcrumb link |
|
3 |
Scenario 3: Update breadcrumb structure on /brands/ pages Given I am on a /brands/ page When I view the breadcrumb Then the breadcrumb should follow the structure "Saclàb > Shop Designer Handbags > Brand Name" Example: On the /brands/chanel page, the breadcrumb should read "Saclàb > Shop Designer Handbags > Chanel" |
This story aims to enhance the user experience by automatically linking guest checkout orders to existing user accounts based on email matching. When a user completes a guest checkout using an email associated with an existing account, the system should automatically link the order to the user’s account. This enables users to see and manage all their orders in one place, even if some were made without logging in.
If a user checks out without logging in but uses an email address that already exists in the database, the order should be automatically linked to their account.
When the user logs into their account, they should be able to see all their orders, including those made without logging in.
This linkage should happen seamlessly without requiring further actions from the user.
As a user,
I want orders made with my email address, even when not logged in, to appear in my account
So that I can view and manage all my orders in one place.
–
|
No |
Acceptance Criteria |
|---|---|
|
01 |
Scenario: Auto-link guest checkout order to an existing user account by email matching |
How to use this page
The release notes on this page have been generated using the Jira issues macro. Each column of the table represents one of the issue fields you selected to include when you created these release notes in Jira.
To edit any of these fields:
Select Edit or type e to edit this Confluence page.
Select the Jira issues macro table and then select the edit icon.
Select Display options to adjust the columns and number of issues that will appear in your table of issues.
Select Insert to save your changes.
