Website review, no card needed

drinkpak.com logo

drinkpak.com website review

Visit site (opens in a new tab)Reviewed 2 November 202625 issues · 74 checks

This review found 25 issues worth fixing on drinkpak.com, 7 of them high impact, across 74 checks. The most urgent: page weight: 36.0 MB in 46 requests. 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
2.3 s1.1 sMay 9Oct 242.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.3 s
May 16, 20261.3 s
May 23, 20261.3 s
May 30, 20261.3 s
Jun 6, 20261.3 s
Jun 13, 20261.3 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 20261.4 s
Jul 11, 20261.5 s
Jul 18, 20261.4 s
Jul 25, 20261.5 s
Aug 1, 20261.5 s
Aug 8, 20261.4 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.5 s
Sep 5, 20261.4 s
Sep 12, 20261.4 s
Sep 19, 20261.3 s
Sep 26, 20261.3 s
Oct 3, 20261.7 s
Oct 10, 20261.9 s
Oct 17, 20262.0 s
Oct 24, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
119 ms74 msMay 9Oct 24114 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202679 ms
May 16, 202680 ms
May 23, 202680 ms
May 30, 202681 ms
Jun 6, 202683 ms
Jun 13, 202682 ms
Jun 20, 202685 ms
Jun 27, 202683 ms
Jul 4, 202683 ms
Jul 11, 202682 ms
Jul 18, 202681 ms
Jul 25, 202683 ms
Aug 1, 202684 ms
Aug 8, 202686 ms
Aug 15, 202686 ms
Aug 22, 202685 ms
Aug 29, 202686 ms
Sep 5, 202686 ms
Sep 12, 202687 ms
Sep 19, 202687 ms
Sep 26, 202683 ms
Oct 3, 202690 ms
Oct 10, 202698 ms
Oct 17, 2026106 ms
Oct 24, 2026114 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 drinkpak.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. drinkpak.com at 0.4 s0.4 s
  2. drinkpak.com at 0.8 s0.8 s
  3. drinkpak.com at 1.2 s1.2 s
  4. drinkpak.com at 1.5 s1.5 s
  5. drinkpak.com at 1.9 s1.9 s
  6. drinkpak.com at 2.3 s2.3 s
  7. drinkpak.com at 2.7 s2.7 s
  8. drinkpak.com at 3.1 s3.1 s

Speed

7 to fix63
  • Render-blocking requests

    3.0 s

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

  • Use efficient cache lifetimes

    34.9 MB

    17 files are served with short cache lifetimes, so returning visitors download them again (34.9 MB).

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, website-files.com and Clarity and others), adding 36.0 MB and 587 ms of main-thread time.

  • website-files.com adds 182 ms

    182 ms

    website-files.com costs a phone 182 ms of main-thread work and 35.6 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 63

    63/100

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

  • Reduce unused JavaScript

    450 ms · 208 KiB

    About 208 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Google Tag Manager adds 242 ms

    242 ms

    Google Tag Manager costs a phone 242 ms of main-thread work and 298 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • 5 long tasks on the main thread

    5 long tasks block the main thread while loading, the longest for 147 ms. During a long task the page ignores taps.

  • Reduce unused CSS

    35 KiB

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

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

  • 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.

2 checks passed
  • Main-thread work: 1.5 s

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

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

7 to fix100
  • First Contentful Paint: 5.7 s

    5.7 s

    The first text or image appears after 5.7 s on a phone. Good is under 1.8 s.

  • Largest Contentful Paint: 5.7 s

    5.7 s

    Your largest element takes 5.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “ANY DRINK. ANY CAN. ANY TIME. ANYWHERE.”. Most of its time is element render delay (2.3 s).

  • Speed Index: 6.8 s

    6.8 s

    Visually, the page fills in at 6.8 s (Speed Index). Good is under 3.4 s.

  • Time to Interactive: 7.5 s

    7.5 s

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

  • Tap response (INP) got 38% slower for real visitors

    +38%

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

  • Largest content (LCP) got 58% slower for real visitors

    +58%

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

  • 3 images without width and height

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

8 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.8 s

    1.8 s

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

  • Real-user INP: 96 ms

    96 ms

    Real visitors wait 96 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.6 s

    1.6 s

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

  • Real-user TTFB: 505 ms

    505 ms

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 62 ms

    62 ms

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

Images and page weight

1 to fix70
  • Page weight: 36.0 MB in 46 requests

    36.0 MB

    Your homepage downloads 36.0 MB in 46 requests on a phone: media 34.6 MB (6), scripts 606 KiB (15) and images 582 KiB (12). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

    1 image further down the page (98 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 10.2 g of CO₂ per visit

    10.21 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

2 to fixGoogle 9798
  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 3 links without text

    3 visible links have no text or label, so screen readers cannot say where they go.

2 checks passed
  • Every image has alt text

    All 34 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

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

SEO

2 to fixGoogle 10092
  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Structured data has 1 problem

    Structured data found (Organization) but with 1 problem, for example “Organization: url is not an absolute URL ("/")”.

  • 51 internal links, 6 external

    The homepage links to 51 pages on drinkpak.com and 6 external pages.

6 checks passed
  • Meta description: 155 characters

    Your meta description is 155 characters: “DrinkPAK manufactures and packages canned beverages for growing brands and retailers, with flexible formats, advanced p…”.

  • One H1 headline

    Your main headline reads: “Any Drink. Any Can. Any Time. Anywhere.”.

  • Title: 49 characters

    Your title is a healthy 49 characters: “Canned Beverage Contract Manufacturing | DrinkPAK”.

  • 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://www.drinkpak.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.drinkpak.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.

  • Text is in the HTML

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

Other pages

1 to fix93
  • 2 pages share a title

    / and https://www.drinkpak.com/solutions/contract-manufacturing all use the title “Canned Beverage Contract Manufacturing | DrinkPAK”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page with very little text

    https://www.drinkpak.com/network has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10087
  • 3 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix70
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 263 words of copy

    The homepage carries about 263 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CONTACT”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact” and “Join the Pak”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Microsoft Clarity (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 5 cookies set on arrival

    5

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

  • No consent tool detected

    No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

  • 13 other companies contacted

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

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 drinkpak.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
Webflow
Analytics
Google Tag Manager
Hosting
Webflow

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on drinkpak.com, including 14 speed issues, 2 SEO issues and 2 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