Website review, no card needed

dipammo.com logo

dipammo.com website review

Visit site (opens in a new tab)Reviewed 9 November 202630 issues · 84 checks

This review found 30 issues worth fixing on dipammo.com, 9 of them high impact, across 84 checks. The most urgent: 25 text elements with low contrast. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.6 s1.5 sAug 15Oct 311.6 s
Show as table
DateReal-visitor load time (LCP)
Aug 15, 20261.6 s
Aug 22, 20261.5 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.5 s
Sep 19, 20261.6 s
Sep 26, 20261.5 s
Oct 17, 20261.5 s
Oct 31, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
73 ms70 msAug 15Oct 3173 ms
Show as table
DateReal-visitor tap response (INP)
Aug 15, 202673 ms
Aug 22, 202672 ms
Aug 29, 202671 ms
Sep 5, 202671 ms
Sep 12, 202671 ms
Sep 19, 202671 ms
Sep 26, 202671 ms
Oct 17, 202670 ms
Oct 31, 202673 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of dipammo.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. dipammo.com at 0.4 s0.4 s
  2. dipammo.com at 0.8 s0.8 s
  3. dipammo.com at 1.1 s1.1 s
  4. dipammo.com at 1.5 s1.5 s
  5. dipammo.com at 1.9 s1.9 s
  6. dipammo.com at 2.3 s2.3 s
  7. dipammo.com at 2.6 s2.6 s
  8. dipammo.com at 3.0 s3.0 s

Speed

3 to fix76
  • Mobile performance score: 76

    76/100

    Your mobile performance score is 76. Pages that score under 90 lose visitors before the first paint.

  • Improve image delivery

    600 ms · 369 KiB

    9 images could be 369 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

  • 1,546 HTML elements

    The page has 1,546 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Render-blocking requests

    200 ms

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 200 ms.

  • 5 third-party services on the page

    5 third-party services load with your homepage (cdn-cookieyes.com, Shopify and Google Fonts and others), adding 100 KiB and 75 ms of main-thread time.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 50 ms. During a long task the page ignores taps.

  • Reduce unused CSS

    13 KiB

    About 13 KiB of CSS is downloaded but never applied on this page.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Use efficient cache lifetimes

    1 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (1 KiB).

2 checks passed
  • Main-thread work: 2.0 s

    A phone's processor spends 2.0 s on main-thread work while loading, 815 ms of it running JavaScript. That is comfortably low.

  • Server response: 7 ms

    7 ms

    Your server sent the HTML in 7 ms, well inside Google's 600 ms guideline.

Core Web Vitals

3 to fix100
  • Largest Contentful Paint: 7.1 s

    7.1 s

    Your largest element takes 7.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 7.2 s

    7.2 s

    The page becomes fully interactive after 7.2 s. Good is under 3.8 s.

  • 1 image without width and height

    1 image have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    -1%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 73 ms to 73 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    0%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

10 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.9 s

    1.9 s

    Real visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 71 ms

    71 ms

    Real visitors wait 71 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.0 s

    1.0 s

    Real visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 551 ms

    551 ms

    Real visitors wait 551 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Speed Index: 2.6 s

    2.6 s

    Visually, the page fills in at 2.6 s (Speed Index), inside the 3.4 s “good” threshold.

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix85
  • Page weight: 2.0 MB in 195 requests

    2.0 MB

    Your homepage downloads 2.0 MB in 195 requests on a phone: images 828 KiB (19), other files 722 KiB (77) and scripts 302 KiB (74). Under 2 MB keeps phones on slow connections fast.

  • 3 images in older formats

    3 images (300 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • About 0.6 g of CO₂ per visit

    0.58 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.58 g of CO₂e: 69.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

7 to fixGoogle 8589
  • 25 text elements with low contrast

    25 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Links must have discernible text (5 elements)

    Links must have discernible text: 5 elements on the page fail this check, rated serious by axe-core.

  • Scrollable region must have keyboard access (2 elements)

    Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (50 elements)

    All page content should be contained by landmarks: 50 elements on the page fail this check, rated moderate by axe-core.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (3 elements).

1 checks passed
  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9286
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “Please verify your age”). One clear main headline is easier for people and search engines.

  • Meta description is long (302 characters)

    Your meta description is 302 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 52 internal links, 12 external

    The homepage links to 52 pages on dipammo.com and 12 external pages.

5 checks passed
  • Title: 30 characters

    Your title is a healthy 30 characters: “AMMO – AMMO | Nicotine Pouches”.

  • Canonical URL set

    The canonical URL is https://dipammo.com/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://dipammo.com/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (691 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://dipammo.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

6 to fix55
  • 1 page without a title

    https://dipammo.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://dipammo.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages share a title

    https://dipammo.com/collections/ammo-nicotine-pouches/products/natural-5-can-log and https://dipammo.com/collections/ammo-nicotine-pouches/products/mint-5-can-log all use the title “Mint | AMMO Nicotine Pouches – AMMO | Nicotine Pouches”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 6 pages without a meta description

    https://dipammo.com/pages/contact, https://dipammo.com/pages/wholesale-application, https://dipammo.com/customer_authentication/redirect, https://dipammo.com/policies/privacy-policy, https://dipammo.com/policies/shipping-policy and https://dipammo.com/policies/refund-policy have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 links to non-canonical URLs

    Your homepage links to 6 pages by a URL that isn't their canonical one, for example https://dipammo.com/collections/ammo-nicotine-pouches/products/wintergreen-5-can-log, whose canonical is https://dipammo.com/products/wintergreen-5-can-log. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://dipammo.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://dipammo.com/customer_authentication/redirect took over 3 s to send its HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 16 found) and read each the way a search engine does.

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

3 to fixGoogle 9671
  • 1 broken image

    1 image failed to load on a phone, for example https://cdn.shopify.com/s/files/1/0894/0224/5394/files/warning.png?v=1758908389.

  • 15 small tap targets

    15 of 38 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix78
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • About 496 words of copy

    The homepage carries about 496 words of visible text.

6 checks passed
  • 11 calls to action

    The homepage has 11 calls to action, for example “Shop now”, “Contact” and “Apply for Wholesale”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 46 testimonial or review blocks and a star rating.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 2 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

  • 7 cookies set on arrival

    7

    Opening the homepage sets 7 cookies (measured from a US location before any click).

  • 7 other companies contacted

    Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) loads with the page.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at dipammo.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 2 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Az Google Font Custom Fonts · Agechecker Net Age Verifier

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on dipammo.com, including 6 speed issues, 3 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25