A practical plan to help Indian shoppers find Nukka, choose the right coffee and place an order with confidence.
A solid foundation.
Important gaps
before the sale.
Nukka has a strong identity, useful coffee details and familiar payment options. The main gaps are in Google search, product choice, customer trust and mobile speed. Make pack value, delivery to the buyer’s PIN code and the full cost clear before checkout.
Help people understand Nukka on Google, give Google clear product details, and answer delivery and return questions before customers pay.
The homepage title is only “nukka”. It needs a short description explaining that Nukka sells whole beans, pour-over bags and instant coffee.
Why this is a priority: a new customer seeing the brand on Google may not know what it sells or why to open the website.
Read finding 01 →The developer needs to add product name, brand, INR price and stock in a standard format behind each page.
Why this is a priority: Google and shopping tools need these details to understand the products and show useful information about them.
Read finding 02 →The tested delivery, refund and terms links do not open working pages. Explain delivery areas, time, charges, COD fees and how to get help.
Why this is a priority: customers need to know when their coffee will arrive and what happens if there is a problem.
Read finding 03 →Higher scores mean a stronger area. Lower scores mean more work is needed. Use the descriptions beside each score to understand what it covers.
Can Google reach the pages and understand their structure?
Do titles and descriptions clearly explain the coffee?
Can an assistant understand Nukka and its coffee range?
Are the brand, INR price and stock supplied in a standard format?
Are pack value, reviews and delivery details clear?
Is the store easy to read, browse and use?
These are audit ratings out of 100. They are not sales results or loading-speed test scores. See Store checks for the measured speed results.
At each step, customers need a simple answer: what is this coffee, which one should I buy, what will I get, and how do I pay?
The logo and brand line stand out. But a new visitor has to look further to understand the types of coffee Nukka sells.
What to improveAdd one short line about beans, pour-over bags and instant coffee. Keep Shop Coffee easy to find.
The homepage shows roast and taste details. The coffee lists give less help comparing products or knowing how to brew them.
What to improveExplain which coffee suits milk, black coffee or a quick cup, and what equipment is needed.
Prices and buy buttons are clear. Pack size, customer reviews and expected delivery dates need to be easier to find.
What to improveShow weight or bag count beside the price. Add reviews and delivery help for the customer’s PIN code near the buy button.
Customers can check out without an account. Razorpay, COD, discounts and free-shipping progress are available.
What to improveMake GST and the ₹49 COD fee clear before checkout. Confirm that UPI, card and COD orders work for supported PIN codes.
Bring taste, equipment, pack size and value into view so shoppers can choose the right coffee for their daily routine.
Product pages explain roast, blend and taste. Show the pack weight next to the price.
Improve the choice: explain the grinder and brewing equipment needed, then compare the three roasts.
Product pages explain the five-bag format and “Tear · Hang · Pour”. Bring this explanation to the collection page too.
Improve the choice: show how a bag works and what the customer needs to brew at home or at work.
These pages already explain flavour, 25g weight, approximate cups, allergens and steps for milk or water.
Keep the standard: give the other coffee formats the same useful details.
| Coffee | Roast level | Coffee blend | Flavours to expect |
|---|---|---|---|
| Sunday Chill | Light to medium | 100% Arabica | Rich floral notes |
| Daily Dose | Medium | 75% Arabica25% Robusta | Mild caramel and nutty notes |
| City Fuel | Dark | 70% Arabica30% Robusta | Dark chocolate and roasted nuts |
Based on Nukka’s product details. Add this guide to the coffee listing pages so customers can compare without opening every product.
Nukka’s language has character. Add simple buying information around it, so a new customer quickly understands the coffee.
“Coffee for ideas
& detours.”
A memorable line. It needs a short explanation of the coffee range beside it.
Your coffee.
Your kind of detour.
Whole beans, pour-over bags and instant coffee. Pick your cup by taste and the way you brew.
Shop the coffee
Keep the existing brand line if preferred. Use the product explanation as the next sentence.
Keep the name people remember. Add the coffee type so it makes sense on the page and in Google.
Put useful taste and blend details near the price. Explain milk or black-coffee use where the product guidance supports it.
Talk about taste, brewing ease and freshness in simple terms. Keep the story focused on what the customer gets from the coffee.
Checks of mobile speed, reading comfort, cart totals, payment options and delivery charges. The results below show what worked, what needs fixing and where only part of the journey was checked.
The main gaps are a slow first screen, small coffee labels and charges explained too late. Cart totals and free-shipping progress worked in the test.
Read the mobile speed finding →The main content took this long to appear on a simulated slow 4G connection. Mobile speed score: 67/100.
The same homepage loaded much faster in the desktop test. Desktop speed score: 96/100.
Roast, blend and taste labels are very small on a phone. Make them bigger so shoppers can compare coffees.
The weakest label/background contrast was 2.81:1, below the 4.5:1 target for normal text. Use darker text.
PageSpeed test: 05 Oct 2026, 23:28 IST. Mobile used a simulated Moto G Power on slow 4G. These scores describe one automated homepage test, not every customer’s experience. Actual customer loading data was unavailable. Coffee labels were measured on a 375px-wide screen.
Lighthouse 13.5.0 · FCP 3.4s · Speed Index 5.1s · TBT 20ms · CLS 0 · Accessibility: 90 mobile / 93 desktop. View the full PageSpeed results.
Each result below says what was found and the next action. Open the linked finding for screenshots and more detail.
What we foundThe homepage needs a clearer title and description for Google. Whole Beans gives little help choosing a coffee. City Fuel does not show pack weight beside its price.
What to doExplain what each coffee is, who it suits and how much comes in the pack. Put the main details near the price and buy button.
What we foundRoast, blend and taste labels are only 9.28px and look faint. Some footer text is faint too. The checked homepage and instant page fit a narrow phone screen.
What to doIncrease label size and use a darker brand colour. Customers should be able to compare coffees without zooming in.
What we foundThe mobile menu and search worked in the checked steps. But a screen reader calls the minus button “Search”, slide dots are hard to tap, and a hidden offer link can still be selected with a keyboard.
What to doCorrect the minus-button name, enlarge the dots’ tap areas and remove the extra hidden link from keyboard navigation.
What we foundTwo City Fuel packs totalled ₹1,298, with ₹201 left for free shipping. Three packs totalled ₹1,947 and showed free shipping. Quantities stayed the same when moving between pages.
What to doKeep these working features. Fix the price that runs past the edge on a very narrow phone screen. Test items were removed after the check.
What we foundGuest checkout, Razorpay and COD were visible. Invalid PIN codes and offer codes showed errors. DETOUR15 reduced ₹1,947 to ₹1,654.95 before any other charges.
What to doShow the ₹49 COD fee earlier. Completed payments and orders were not tested; no customer details, order or payment were submitted.
What we foundThe brewing video keeps playing and has a sound button, but no visible pause button. The moving offer strip pauses on mouse hover, which phone users cannot use.
What to doAdd a pause button that works on a phone and with a keyboard. Allow customers who prefer less movement to read a still version.
Six parts of the journey, from finding Nukka to placing an order.
Google listings, search descriptions, headings, page code, sitemaps, duplicate pages and AI shopping information.
Homepage message, brand story, product names, offers and clear shopping buttons.
Beans, pour-over and instant; taste, roast, brewing, equipment, pack size and price.
Phone loading speed, readable text, menus, search, screen-reader support and easy-to-tap controls.
Cart totals, discounts, gift and free-shipping limits, PIN-code delivery, UPI/cards, COD fees, GST, policies and reviews.
46 findings with screenshots and fixes, a 30-day action plan, team owners and ideas for repeat orders and larger baskets.
Each finding explains the issue, why it matters, what to change and how to check the fix. Use the severity level to decide what to do first.
All 46 findings matter. Open them below to read the issue, why it matters, the fix and the screenshot proof. Use filters only when looking for a specific issue.
Fix first. A basic search or buying-trust issue.
Next priority. A clear problem with choice, trust or usability.
Plan next. Helps customers choose or removes buying friction.
Later. A smaller fix or an idea to test.
Each image starts with “What this image shows”. Read that first, then look at the numbered red boxes. Some findings have more than one image because they compare pages or include a check behind the page.
“Not seen in the checked area” refers to the pages inspected. “Improvement to test” is a suggestion to try and measure, rather than a broken feature.
Download all screenshots · Detailed code checks for the developer
The title used for Google is only “nukka”. The homepage has no short Google description, and its main headline is not marked as the main heading in the page code.
Someone searching for coffee may see the brand name without knowing what Nukka sells. This affects the store’s main entry page.
Add a clear Google title such as “Nukka Coffee | Whole Beans, Pour Over & Instant Coffee”. Add a short description. Ask the developer to mark the main coffee headline as the page’s main heading (H1).
Check that the homepage has one main heading, a useful title and a search description.
The first screen gives the brand a mood, but does not quickly say what coffee Nukka sells.
The homepage title says only “nukka”. The page also has no Google description or main heading marked in its code.
This image checks details behind the page that a normal screenshot cannot show. The explanation above is the key point; the table or code is the supporting detail.
The downloaded code of nine product pages had no standard product details for Google. City Fuel stores details for the website’s own use, but not in the standard format checked here.
Google and shopping tools may have less clear information about the coffee, INR price and stock. This can limit the useful product details they show.
Ask the developer to add standard product details for Google: name, brand, price in INR, stock and the correct product link. Add the brand details on the homepage too.
Use Google’s product-data test. Check that the price, stock and product links match what customers see.
This is where customers see the coffee, price and buy buttons. Google needs the same details in a standard format behind the page.
The code from nine product pages had no standard product details for Google, such as product name, INR price and stock.
This image checks details behind the page that a normal screenshot cannot show. The explanation above is the key point; the table or code is the supporting detail.
The shipping, refund and terms URLs each returned 404. The checked footer links only the Privacy Policy.
Before paying, shoppers need to know delivery charges, return conditions and how to get help. Missing pages leave these basic questions unanswered.
Publish clear policies covering Indian delivery areas, dispatch time, shipping charges, COD fees, cancellations, damaged packs and applicable returns. Link them near buying controls and in the footer.
Open all policy links. A customer should be able to understand the charges, timelines and next steps.
The tested shipping-policy link opens a “page not found” screen instead of delivery information.
All three tested links—shipping, refunds and terms—were unavailable.
This image checks details behind the page that a normal screenshot cannot show. The explanation above is the key point; the table or code is the supporting detail.
The checked homepage, collection cards and product buying areas show no reviews or ratings.
A first-time customer has little help judging taste, pack quality or delivery experience. Reviews can make trying a new coffee brand easier.
Ask customers for reviews after delivery. Show taste and brewing feedback, ratings and customer photos on relevant product pages.
Reviews are easy to read on mobile and appear beside the coffee they describe.
No customer rating or review summary is visible beside these buy buttons.
The checked coffee list shows product names and prices, with no customer ratings.
“Coffee for ideas & detours.” gives the brand a mood, but does not quickly explain the coffee options or their benefit.
A new visitor has to scroll to find out whether this is coffee for their daily cup, milk coffee or a quick brew.
Keep the brand line. Add one simple line about whole beans, pour-over bags and instant coffee, with a clear Shop Coffee button.
A first-time visitor can understand what Nukka sells and where to start within a few seconds.
A new visitor sees a brand line, but has to look further to understand the coffee options.
The homepage promises “Sourced Honestly”. Our Story focuses on the feeling around coffee, with little detail about what makes Nukka’s coffee worth trying.
The story builds a mood, but gives a new customer few practical reasons to choose the brand.
Explain the taste Nukka aims for, how its coffee fits everyday routines and how freshness is handled. Use short, customer-facing details the brand is comfortable sharing.
The story gives two or three clear reasons to try Nukka, alongside its existing personality.
The homepage makes a broad brand promise. More useful coffee details would give customers a reason to try Nukka.
Our Story describes moments around coffee. It could also explain what customers will enjoy about Nukka.
Titles and main headings use names such as City Fuel and No Detours. The coffee type is explained further down the page.
A shopper arriving from Google may not know whether the product is whole bean, pour-over or instant coffee.
Keep each product name and add its format, roast or flavour. For example: “City Fuel — Dark Roast Espresso Blend”. Use similar wording in search titles and image descriptions.
A customer can identify the coffee type from its title without reading the full page.
The product title says “City Fuel”. The coffee type appears further down in the description.
The search titles use product names without clearly naming the coffee type.
This image checks details behind the page that a normal screenshot cannot show. The explanation above is the key point; the table or code is the supporting detail.
/pages/contact and /pages/contact-us show the same contact information. Both links work, and both tell Google that they are the main version.
Two copies make it harder for search tools to know which page to show. It also adds maintenance work.
Choose one Contact page. Send the second link to that page and update the menu and Google’s list of store pages.
The old link opens the chosen Contact page, and the store links to only that page.
This is the Contact page at /pages/contact.
A second link, /pages/contact-us, shows the same contact information.
Both Contact links work, and both tell Google to treat themselves as the main page.
This image checks details behind the page that a normal screenshot cannot show. The explanation above is the key point; the table or code is the supporting detail.
Whole Beans opens into a product grid with names, prices and filters, but little help choosing a roast or understanding the format.
Someone moving from instant coffee to beans may not know what equipment they need or which blend to try first.
Add a short format guide and roast comparison above the grid. Explain equipment needs and milk/black-coffee suitability where the product details support it.
The page explains how to use the format and how to choose between the coffees.
Whole Beans opens straight into products and prices, with little help choosing a coffee.
The checked collection pages and Our Story have no short description for Google. Whole-bean descriptions are about 320–328 characters long.
The most useful product information may be hard to spot in Google’s short preview.
Write a short, different search description for each key page. Lead with the coffee type and benefit; put the main point early.
Each key page has a clear description with the main point first. Check Google’s preview after it picks up the changes.
The checked collections and Our Story have no Google description. Product descriptions are long enough that the main point may be hard to spot.
This image checks details behind the page that a normal screenshot cannot show. The explanation above is the key point; the table or code is the supporting detail.
Product details explain roast and taste, but leave questions about grind, storage, shelf life and freshness unanswered. Instant pages already have useful brewing steps.
A buyer may hesitate if they do not know how to use or store the coffee once it arrives.
Add short answers about equipment, grind, milk or water preparation, storage and shelf life. Put stock availability near the buy button.
Customers can find the answers they need before adding the coffee to their cart.
Roast and taste are explained, but everyday questions about storage, shelf life and freshness still need answers.
The instant page already gives useful brewing steps and a 25g pack size.
City Fuel’s stored brand name says “My Store”. Its stored roast tag says Medium Roast, while the description customers read says dark roasted.
Search feeds and shopping tools may show the wrong brand or roast.
Set the stored brand name to Nukka. Keep roast, coffee format, pack size and descriptions the same across the website and shopping feeds.
A catalogue export and the website show the same brand and coffee details.
City Fuel’s stored brand and roast details do not match its page description.
This image checks details behind the page that a normal screenshot cannot show. The explanation above is the key point; the table or code is the supporting detail.
The product description calls City Fuel dark roasted.
Whole-bean weight is shown on pack photos rather than beside the price. Collection cards omit weight or bag count. Instant copy includes 25g and cup yield.
A buyer cannot quickly compare ₹ per pack or the number of cups they can expect. Pack text is hard to read on a phone.
Show the confirmed weight or bag count beside every price. For instant coffee, include the approximate cup yield; add price per cup if the serving size supports it.
Cards, product pages and the cart make quantity and price clear together.
The price is clear, but the pack weight is not written beside it.
The coffee list shows prices without weight or bag count.
The checked product buy areas have no nearby dispatch or delivery estimate.
A buyer planning for an office, home or gift order does not know when the coffee will arrive.
Add a PIN-code delivery check if available. Otherwise show a clear dispatch range and explain how delivery time varies by location.
Customers can see a useful delivery estimate and supported area before checkout.
Customers can buy here, but there is no nearby estimate of when their order will arrive.
Razorpay and COD are visible at checkout, but there is no clear payment-options row beside the checked product buying controls.
A buyer may leave before finding the payment method they prefer.
Add a small payment row near Add to Cart: UPI and cards through Razorpay, plus COD where available. Link to COD charges and delivery rules.
The product page shows the payment options that the checkout actually supports.
The product buying area does not clearly show which payment methods are available.
Razorpay and COD appear after the customer enters checkout.
Instant pages have an Allergen Information section. The checked whole-bean and pour-over areas do not. A readable FSSAI licence detail was not found in the checked page areas.
Customers need clear food information, especially when choosing flavoured coffee or buying for someone else.
Have the operations team check ingredients, allergens and applicable FSSAI details against the packaging. Present the relevant information consistently on product pages.
Product-page details are easy to read and agree with the packs. This check covers the website, not a full compliance review.
The instant page clearly includes an allergen answer.
The checked whole-bean section does not show the same allergen information or a readable FSSAI licence detail.
The checked pour-over details explain the coffee and brewing, but have no matching allergen section.
https://nukka.in/products/city-fuel-pour-over?variant=48094007165146
City Fuel has no clear Whole Bean / Pour Over switch near the buy buttons. Related products can appear in the general recommendations further down.
A buyer may like the roast but miss the version that suits their equipment or routine.
Add a clear link between matching bean and pour-over products near the purchase controls.
A buyer can switch to the same coffee in another format in one step.
There is no clear switch from this whole-bean coffee to its pour-over version beside the buy buttons.
The homepage has roast, blend and tasting-note cards. Whole Beans collection cards do not show that comparison.
Customers browsing a collection have to open several pages to compare coffees.
Reuse the homepage facts in a small roast guide. Help shoppers choose by flavour, brew method and milk/black-coffee use where supported.
Customers can compare the three roasts without opening three product pages.
Customers must open several product pages to compare roasts and equipment needs.
The checked product details have no clear caffeine or decaf answer. “Sunday Chill” is a mood-led name.
A buyer looking for decaf or less caffeine needs a direct answer before choosing.
State whether each coffee is decaf. Add measured caffeine information if available; otherwise keep the answer simple.
Customers can tell the difference between a mood name and the product’s caffeine information.
The checked Sunday Chill details do not clearly say whether the coffee is decaf.
https://nukka.in/products/sunday-chill?variant=48094007099610
The store has files and links for AI shopping tools. The checked file mainly explains how to use the shopping system, with little introduction to Nukka’s coffee range.
A shopping assistant has less useful context when matching Nukka to a customer’s coffee needs.
Add a short introduction covering the brand, coffee formats, INR pricing, Indian delivery and where to find payment and policy details.
The information matches the store and gives a clear summary of the coffee range.
The file for AI shopping tools explains how to use the store, but gives little introduction to the coffee range.
This image checks details behind the page that a normal screenshot cannot show. The explanation above is the key point; the table or code is the supporting detail.
The checked product sections are Meet Your Coffee, Best For and Coffee Mood, with no short question-and-answer section.
Common buying questions are harder to find, even when some answers are already in the page copy.
Answer questions such as “Do I need a grinder?”, “Can I make this with milk?”, “How many cups does this pack make?” and “Is COD available at my PIN code?”.
Answers are short, easy to find and specific to the product or delivery area.
The product has named sections, but no short questions-and-answers area.
Each checked product page has 11 images in its code. Five have an empty or missing written description. This includes decorative images and small gallery previews. Several others use only the product name.
People using screen readers may miss useful pack or brewing information.
Write short descriptions for photos that explain the coffee, pack or brewing steps. These are called alt text and are read aloud by screen readers. Decorative images can stay without descriptions.
A screen-reader user can understand the useful differences between the product images.
These product photos need useful descriptions for people who hear the page through a screen reader.
Some product images have no written description in the page code.
This image checks details behind the page that a normal screenshot cannot show. The explanation above is the key point; the table or code is the supporting detail.
After the main product heading, the page jumps straight to much smaller section-heading levels. In the code, this is a jump from H1 to H4.
People using screen readers may find it harder to move through the product sections.
Ask the developer to use the next heading level for main product sections (H2), and the level after that for smaller sections (H3). Keep a clear reading order.
A heading check shows a sensible order from the product title through its details.
The product sections use a lower heading level than expected after the main product title.
The page jumps from heading level 1 to level 4.
This image checks details behind the page that a normal screenshot cannot show. The explanation above is the key point; the table or code is the supporting detail.
The checked buy area offers a one-time purchase, with no recurring-order option.
Customers may want to buy their usual coffee again without repeating every step.
Start with a clear Buy Again route or refill reminder. Consider a monthly subscription if delivery, margins and customer demand support it. Explain payment and cancellation clearly.
Compare repeat orders and margins before rolling out the option more widely.
Customers can place a one-time order here. An easier way to buy their usual coffee again could be tested.
The homepage advertises a free coffee pin above ₹999. The checked cart shows progress towards ₹1,499 free shipping, but no pin reminder or relevant bundle.
A buyer can forget the gift or miss an easy way to reach the free-shipping amount.
Show progress towards both active offers. Test a relevant add-on or tasting bundle, with the offer rules clear after discounts.
Check the ₹999 and ₹1,499 limits, discount rules and cart messages. Compare order value and completed checkouts.
The homepage promotes a free coffee pin for orders above ₹999.
The cart shows free-shipping progress, but no reminder of the pin offer or a useful add-on in this view.
The closing homepage block has a prominent filled Join Us button for hiring.
The final strong action moves visitors away from buying coffee.
Use a smaller careers link and finish the shopping page with a coffee or product-choice action.
Shopping remains the clearest next step at the end of the homepage.
The final large homepage button leads to hiring rather than coffee shopping.
After the main buy area scrolls out of view, no fixed Add to Cart button is visible in the checked mobile page.
A customer reading further down has to scroll back to buy.
Test a compact Add to Cart bar on mobile. Keep price and product name clear, without covering the page or other controls.
The button adds the right product and is easy to use on a small phone.
After scrolling down the mobile product page, the buy buttons are no longer on screen.
The product page places the gallery and buying details side by side.
Some new visitors may need more time to find images, details and the buy buttons.
Ask a few first-time shoppers to choose a coffee and add it to the cart. Adjust the layout if they struggle.
Customers can browse the images, read the details and find the buy controls easily.
The desktop page puts photos on the left and buying details on the right.
Following DETOUR15 opens product browsing without an immediate success message in the captured view. The code reduced the total in the checkout test.
A shopper may not know whether the 15% offer worked.
Show a short confirmation once the code is active, and explain any first-order conditions.
The message appears when the code is active and the discount matches the checkout total.
Following DETOUR15 opens product browsing without an immediate discount confirmation in this view. The discount did work in the checkout test.
The offer strip includes “Brew. Connect. Repeat.” and “Let’s Meet Over Nukka.”. Mood-led lines also appear above the coffee cards.
These spaces could also answer a buying question while keeping the brand’s voice.
Mix brand lines with active offers, pack information, delivery help and supported payment options. Make Shop All labels clear about the coffee format.
A quick scan gives the customer useful information as well as brand personality.
The moving top strip mixes brand lines with offers and shipping information.
A brand line appears above the helpful roast cards.
/collections/frontpage shows products under the name “Home page”. It is included in the list of pages for Google, and tells Google it is the main version of that page.
The generic name can make a Google result confusing.
If this collection helps shoppers, give it a clear name and purpose. Otherwise, ask the developer to send it to the right collection or stop Google from listing it.
Customers and Google can tell what the collection is for. Unneeded copies and links are removed.
An extra product collection is called “Home page”, which gives shoppers little information.
This extra collection can be found by Google and points to itself as the main version.
This image checks details behind the page that a normal screenshot cannot show. The explanation above is the key point; the table or code is the supporting detail.
The homepage requests two external files that tell the browser which fonts to load. The mobile speed test also lists files that delay the page appearing.
Extra loading steps can slow the first screen on a phone connection.
Keep Nukka’s fonts. Ask the developer to remove unused font styles and check whether smaller files or loading fonts directly from the store would help.
Compare loading speed before and after. The page should keep the same brand appearance.
The homepage requests two external files that tell the browser which fonts to load.
This image checks details behind the page that a normal screenshot cannot show. The explanation above is the key point; the table or code is the supporting detail.
PageSpeed lists requests that delay the screen and files that depend on other files loading first.
https://pagespeed.web.dev/analysis/https-nukka-in/yra57mv7u5?form_factor=mobile
City Fuel has both HTTP and HTTPS links for its social-share image. All nine product entries in the page list for Google show the same update time.
Image links and update dates should give clear, consistent information to social apps and Google.
Use secure HTTPS links for share images. Check that the page list for Google records actual product updates where Shopify allows it.
Social previews load the right image, and sitemap dates match real updates.
The share-image links use both HTTP and HTTPS. All nine product sitemap entries show the same update time.
This image checks details behind the page that a normal screenshot cannot show. The explanation above is the key point; the table or code is the supporting detail.
City Fuel has an internal product code (SKU), but the barcode field is empty. No other standard product identifier was found in the checked code.
Shopping feeds may need more information to match the product correctly.
Use the codes already assigned to the product where shopping feeds need them. Keep the brand, product code and coffee details the same across the store and feeds.
Assigned identifiers match the catalogue, packs and feeds.
City Fuel has an internal product code, but no barcode or other standard product identifier was found in the checked code.
This image checks details behind the page that a normal screenshot cannot show. The explanation above is the key point; the table or code is the supporting detail.
The News page has a heading but no articles in its current listing.
Useful answers could help people choose and use Nukka’s coffee.
After the main store fixes, add a few useful guides: beans vs instant, easy milk coffee, pour-over bags at work and coffee storage. Link them to the relevant products.
Each guide answers a real question and leads naturally to the right coffee.
The News page has a title but no articles in the checked list.
The footer links Instagram. A wider review of independent brand mentions has not been completed.
A new buyer may look outside the store before trusting a coffee brand.
Keep official profiles up to date. Link useful customer content and relevant independent reviews or features as they become available.
Brand details agree across profiles and the links help a buyer learn more.
The footer links to Instagram. Other independent mentions still need a wider check.
robots.txt and agents.md ask shopping agents to recommend installing a third-party shopping skill.
That promotion adds little information about Nukka’s coffee and buying experience.
Keep these files focused on coffee facts, store links and supported shopping tools. Keep payment approval clear.
An assistant can find useful store information without promotional installation requests.
The public files ask AI shopping tools to promote the installation of another shopping tool.
This image checks details behind the page that a normal screenshot cannot show. The explanation above is the key point; the table or code is the supporting detail.
In the simulated slow-4G test, the main homepage content took 6.4 seconds to appear. Mobile scored 67/100 for speed. Desktop was faster at 1.3 seconds and 96/100.
A shopper on a slower mobile connection waits several seconds for the main content. This weakens the first impression.
Ask the developer to check what is delaying the first screen, then reduce heavy images, video and font-loading steps. Start with the delays listed in PageSpeed and keep the Nukka fonts.
Repeat the same test on the homepage, product pages and coffee lists. Also track actual customer loading times. Aim for the main content to appear within 2.5 seconds for at least 75% of visits.
In the simulated mobile test, the main homepage content took 6.4 seconds to appear.
https://pagespeed.web.dev/analysis/https-nukka-in/yra57mv7u5?form_factor=mobile
On the checked phone-sized view, Roast, Blend, Notes and Coffee mood labels are only 9.28px and partly faded. Their text/background contrast is about 2.81–3.26:1. Footer red text is also faint, at about 2.86:1.
These labels help people choose coffee. Small, faint text makes comparison harder on a phone.
Increase the label size, remove the fading and use a darker colour from the brand palette. Keep explanations in normal sentence case.
Check on a small phone and with text enlarged to 200%. Ask the developer to meet at least 4.5:1 text/background contrast for normal text, or 3:1 for large text.
Important coffee labels look small and faint on a phone.
The measurements confirm that the labels are small and do not stand out enough from their background.
This image checks details behind the page that a normal screenshot cannot show. The explanation above is the key point; the table or code is the supporting detail.
The footer’s red text is faint against the mustard background too.
The minus button’s hidden label is “Search” on products and in the cart. A screen reader says this label aloud. The plus button correctly says “Increase quantity”.
Someone using a screen reader hears the wrong action when trying to reduce their order quantity.
Change the shared label to “Decrease quantity” and make updated quantities and totals clear.
Check the control with a screen reader on product pages and in the cart.
This minus button reduces the quantity, but a screen reader announces it as “Search”.
The button’s hidden label confirms why a screen reader says “Search”.
This image checks details behind the page that a normal screenshot cannot show. The explanation above is the key point; the table or code is the supporting detail.
The moving offer strip creates a hidden copy of DETOUR15, but that copy remains reachable with the Tab key.
Keyboard users can land on a link that a screen reader does not describe.
Keep one usable offer link. Ask the developer to stop the hidden visual copies being selected with the Tab key. Hiding them from a screen reader alone does not do this.
Tab through the strip. Each offer is reached once and every focused link has a clear name.
The offer strip repeats the same message to keep it moving across the screen.
The hidden extra offer link can still be selected using the Tab key.
This image checks details behind the page that a normal screenshot cannot show. The explanation above is the key point; the table or code is the supporting detail.
The mobile slide dots have tap areas of about 12×9px and are close together. PageSpeed also flags their size or spacing.
A shopper can easily tap the wrong slide on a small phone.
Keep the small visible dots, but make the button area around each one bigger. Ask the developer to meet the 24×24px size or spacing rule; aim for a 44×44px tap area where practical.
Test the real tap areas with touch and keyboard, including product recommendations.
The three slide dots are small and close together, making them easy to miss on a phone.
The measured tap areas confirm that these controls are very small.
This image checks details behind the page that a normal screenshot cannot show. The explanation above is the key point; the table or code is the supporting detail.
With three City Fuel packs, a 320px screen produces a 328px-wide page. The line price and savings label extend past the right edge. The checked 375px view fits.
A buyer may miss part of the price or need to move the page sideways.
Stack or wrap the cart row at narrow widths. Keep price, quantity, Remove and Checkout easy to see.
At 320px, the page fits the screen and all amounts are readable. Check long names and larger text too.
On a very narrow phone, part of the cart price runs past the right edge.
The brew video plays and repeats automatically. Its sound button cannot pause it. The moving offer strip pauses on mouse hover, but still changes every four seconds when reduced motion is selected.
Moving content can make reading harder. A phone user cannot use mouse hover to pause it.
Add pause and play buttons that work on a phone and with a keyboard. Give people who choose less movement a still version. Check whether any spoken video needs captions.
A user can pause the movement and keep reading. Test the browser’s reduced-motion setting.
The brewing video keeps playing. Its visible button changes sound, but cannot pause the video.
The settings confirm that the video plays and repeats automatically, without built-in controls.
This image checks details behind the page that a normal screenshot cannot show. The explanation above is the key point; the table or code is the supporting detail.
Checkout shows “Cash on Delivery (incl. ₹49 COD fee)” and a 3–5-business-day estimate. The checked product and cart areas have no matching COD-fee note.
A late fee can change the buyer’s expected total. Free shipping and a COD fee need separate explanations.
Show the applicable COD fee and PIN-code availability near the buying area and in the shipping policy. Make the delivery and payment choices easy to understand.
Test prepaid and COD orders for supported PIN codes, below and above ₹1,499, including after discounts. Rates shown with an invalid PIN need further checking.
Checkout introduces the ₹49 COD fee and a delivery estimate. The product and cart views did not show the same fee note.
Product pages say “MRP inclusive of all taxes (GST)”. The cart says “Shipping & taxes calculated at checkout”.
The buyer may wonder whether GST will be added to the displayed price.
Check the tax setup, then use matching wording. For example: “GST included. Shipping and any COD fee shown at checkout.”
Product, cart and checkout wording matches the actual tax and charge breakdown.
The product price says GST is included.
The cart says taxes will be calculated at checkout, which conflicts with the product message.
No matching findings. Try another word or severity.
Checked 05–06 October 2026. Open each finding for marked screenshots and source details. Delivery exceptions, completed payments and sales data need store-team access.
A suggested order for the team. Start with search, policies, mobile speed and reading comfort. Then improve product choice and test growth ideas.
Fix search, product data and policies. Improve the slow mobile first screen and small labels.
Make coffee choice, pack value, reviews and delivery details easy to find.
Clean up page data and track buying steps before adding more features.
Tick a task when the team has completed it. Progress is stored locally in this browser when available.
The store has several useful features already. Build on them as you improve search, coffee choice and checkout clarity.
Shop Coffee, Add to Cart and Buy It Now are easy to understand. Keep their strong appearance while fixing the minus-button label and small slide controls.
DETOUR15 reduced the total at checkout. Free-shipping progress updated as cart quantities changed.
Guest checkout, Razorpay and COD are visible. Check completed UPI, card and COD orders with the store team before marking the payment flow complete.
Roast, blend and taste notes are useful. Instant products already explain weight, approximate cups, allergens and milk/water preparation.
Product content is available in page code, and the theme uses modern images and lazy loading. Focus the next speed work on the slow mobile result.
The store has sitemaps, crawl rules and agent-shopping links. Keep them up to date as products and buying options change.
Nukkad, detours and mood-led names make Nukka recognisable. Keep that voice and add useful coffee facts around it.
The store shows a phone number, email, Mumbai location and working hours. Keep these easy to find for Indian customers with delivery or order questions.
Store checks dated 05–06 October 2026, focused on the journey from Google or a first visit to checkout.
Checked the homepage, coffee collections, product pages, Our Story, Contact pages, blog and policy links. Page-code checks covered nine product URLs. Buying checks covered search, quantity changes, cart totals, offers and guest checkout.
Desktop and selected 320px, 375px and 768px views were checked. The report includes 32 unedited captures and 73 marked views across 46 findings. Technical images show page-code or browser-property checks and are labelled separately.
Readiness ratings show the overall strength of the store. They are an assessment, rather than sales results. PageSpeed scores come from a separate homepage loading test.
Some recommendations are fixes; others are ideas to test. Use order and traffic data to measure the effect. Full payment completion, delivery exceptions and all-device testing still need store-team access.
No customer contact details, order or payment were submitted during these checks.
SEO: helping people find and understand the store on Google. Structured data: standard page code for products, prices and the brand. CRO: making buying easier and testing the result. AI shopping: helping shopping assistants understand the store. LCP: how long the main content takes to appear. Alt text: image descriptions used by screen readers.