Website review, no card needed

tppackaging.com logo

tppackaging.com website review

Visit site (opens in a new tab)Reviewed 11 November 202621 issues · 72 checks

This review found 21 issues worth fixing on tppackaging.com, 8 of them high impact, across 72 checks. The most urgent: render-blocking 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

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

How it loaded on a phone

  1. tppackaging.com at 0.4 s0.4 s
  2. tppackaging.com at 0.8 s0.8 s
  3. tppackaging.com at 1.2 s1.2 s
  4. tppackaging.com at 1.6 s1.6 s
  5. tppackaging.com at 2.0 s2.0 s
  6. tppackaging.com at 2.4 s2.4 s
  7. tppackaging.com at 2.8 s2.8 s
  8. tppackaging.com at 3.2 s3.2 s

Speed

4 to fix63
  • Render-blocking requests

    1.2 s

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

  • 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

    760 ms · 158 KiB

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

  • Shopify adds 175 ms

    175 ms

    Shopify costs a phone 175 ms of main-thread work and 325 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.

  • 6 third-party services on the page

    6 third-party services load with your homepage (Shopify, Hubspot and usemessages.com and others), adding 506 KiB and 330 ms of main-thread time.

  • Use efficient cache lifetimes

    150 ms · 167 KiB

    10 files are served with short cache lifetimes, so returning visitors download them again (167 KiB).

  • 4 long tasks on the main thread

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

  • Improve image delivery

    30 KiB

    3 images could be 30 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused CSS

    15 KiB

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

  • Legacy JavaScript

    14 KiB

    Polyfills for old browsers add 14 KiB JavaScript that modern phones do not need.

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

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 1.7 s

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

  • Server response: 6 ms

    6 ms

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

Core Web Vitals

4 to fix73
  • First Contentful Paint: 5.2 s

    5.2 s

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

  • Largest Contentful Paint: 5.2 s

    5.2 s

    Your largest element takes 5.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Your Global Partner for Disposable Single-Use Packaging in …”. Most of its time is element render delay (2.5 s).

  • Speed Index: 7.0 s

    7.0 s

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

  • Time to Interactive: 8.3 s

    8.3 s

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Total Blocking Time: 153 ms

    153 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix97
  • An image on the first screen is lazy-loaded

    banner-new2_2.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 0.5 g of CO₂ per visit

    0.47 g

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

3 checks passed
  • Page weight: 1.7 MB in 182 requests

    1.7 MB

    Your homepage downloads 1.7 MB in 182 requests on a phone: other files 775 KiB (102), scripts 574 KiB (45) and images 223 KiB (10). That is a lean page.

  • 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 9796
  • 11 text elements with low contrast

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

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 21 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

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

SEO

4 to fixGoogle 9275
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is long (73 characters)

    Your title is 73 characters, so Google will cut it off around 60: “Thermal & Protective Packaging Inc. – Thermal & Protective Packaging Inc.”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • One H1 headline

    Your <h1> is empty.

  • 59 internal links, 0 external

    The homepage links to 59 pages on tppackaging.com and 0 external pages.

4 checks passed
  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization and WebSite.

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

AI search readiness

100
4 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: 4 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix90
  • 14 pages without a meta description

    https://tppackaging.com/pages/portfolio, https://tppackaging.com/collections/approved-lsg-materials, https://tppackaging.com/collections/disposable-food-service, https://tppackaging.com/collections/bags-liners, https://tppackaging.com/collections/janitorial-paper-products and https://tppackaging.com/collections/industrial-safety-products and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages without an H1

    https://tppackaging.com/pages/portfolio, https://tppackaging.com/pages/services, https://tppackaging.com/pages/about-us, https://tppackaging.com/pages/warehouse-locations and https://tppackaging.com/pages/contact have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

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

  • Titles are unique

    Every page we checked has its own title.

  • 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

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

2 checks passed
  • Tap targets are thumb-sized

    21 of 21 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix81
  • 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.

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

  • 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 393 words of copy

    The homepage carries about 393 words of visible text.

5 checks passed
  • Clear next step on the first screen

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

  • 7 calls to action

    The homepage has 7 calls to action, for example “Contact”, “Get In Touch” and “Learn More”.

  • 3 short forms

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

  • Direct contact links

    Visitors can reach you directly: 4 phone links and 1 email link.

  • Phone number on the homepage

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

Privacy and tracking

  • 1 tracker load before any consent

    1

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

  • 8 cookies set on arrival

    8

    Opening the homepage sets 8 cookies, 1 of them by other companies (measured from a US location before any click).

  • 11 other companies contacted

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

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) 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 tppackaging.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

O Request A Quote · hubapi.com

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 21 issues on tppackaging.com, including 8 speed issues, 4 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