Website review, no card needed

directpapersupply.com logo

directpapersupply.com website review

Visit site (opens in a new tab)Reviewed 7 November 202628 issues · 78 checks

This review found 28 issues worth fixing on directpapersupply.com, 8 of them high impact, across 78 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 directpapersupply.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

5 to fix84
  • Render-blocking requests

    1.4 s

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

  • Mobile performance score: 84

    84/100

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

  • Reduce unused JavaScript

    150 ms · 269 KiB

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

  • 1,540 HTML elements

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

  • Shopify adds 104 ms

    104 ms

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

  • Improve image delivery

    150 ms · 213 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Hubspot and Google Tag Manager and others), adding 850 KiB and 251 ms of main-thread time.

  • Reduce unused CSS

    150 ms · 29 KiB

    About 29 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Use efficient cache lifetimes

    159 KiB

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

  • 2 long tasks on the main thread

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

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

2 checks passed
  • Main-thread work: 1.3 s

    A phone's processor spends 1.3 s on main-thread work while loading, 580 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 fix83
  • Time to Interactive: 9.7 s

    9.7 s

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

  • Largest Contentful Paint: 3.9 s

    3.9 s

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • Speed Index: 3.7 s

    3.7 s

    Visually, the page fills in at 3.7 s (Speed Index). Good is under 3.4 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
  • Cumulative Layout Shift: 0.069

    0.069

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

  • Total Blocking Time: 13 ms

    13 ms

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

Images and page weight

3 to fix69
  • Page weight: 2.5 MB in 250 requests

    2.5 MB

    Your homepage downloads 2.5 MB in 250 requests on a phone: scripts 901 KiB (76), other files 792 KiB (108) and images 518 KiB (22). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    DPS_BANNER_15_1.png 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).

  • 1 image far larger than shown

    33 KiB

    1 image is downloaded at several times the size a phone draws it, for example DPS_BANNER_15_1.png at 1,800 px wide, shown at 350 px. Resized copies would save about 33 KiB.

  • 1 image in older formats

    1 image (36 KiB) is 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.7 g of CO₂ per visit

    0.72 g

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

Accessibility

6 to fixGoogle 9193
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 6 text elements with low contrast

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

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

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

  • 10 links without text

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

  • 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 (h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 39 images in the HTML carry an alt attribute.

  • 54 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 54 passed and 6 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 9274
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (67 characters)

    Your title is 67 characters, so Google will cut it off around 60: “Direct Paper Supply | Paper Rolls, Guest Checks & Business Supplies”.

  • Meta description is long (185 characters)

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

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("https:files/direct-paper.png")”.

  • 188 internal links, 19 external

    The homepage links to 188 pages on directpapersupply.com and 19 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://www.directpapersupply.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.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.directpapersupply.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 (1,134 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix70
  • 3 linked pages are broken

    Your homepage links to https://www.directpapersupply.com/collections/pallet-wrap, https://www.directpapersupply.com/collections/nitrile-gloves and https://www.directpapersupply.com/collections/vinyl-gloves, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 3 pages without a meta description

    https://www.directpapersupply.com/collections/shop-all, https://www.directpapersupply.com/collections/poly-gloves and https://www.directpapersupply.com/collections/can-liners have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

5 checks passed
  • 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.

  • 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 12 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9291
  • 8 small tap targets

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

  • 12 distorted images

    12 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 3 low-resolution images

    3 images are served at too low a resolution for sharp phone screens.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix85
  • 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.

  • About 569 words of copy

    The homepage carries about 569 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

8 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Shop All”, “Contact Us” and “Subscribe”.

  • 3 short forms

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

  • Social proof on the page

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

  • Analytics in place

    Analytics detected: Google Tag Manager and HubSpot.

  • Direct contact links

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

  • Opening hours shown

    Your opening hours are on the homepage.

  • 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

  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and 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.

  • 21 cookies set on arrival

    21

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

  • 25 other companies contacted

    Loading the homepage contacts 25 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 directpapersupply.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 1 app. It is code from another company running for your shoppers.

Apps your storefront loads

O Request A Quote

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

  • The footer still says © 2008.

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on directpapersupply.com, including 9 speed issues, 4 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