odpbusiness.com website review

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

A phone's processor spends 34.0 s on main-thread work while loading, 28.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

Your mobile performance score is 35. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

8 third-party services load with your homepage (officedepot.com, Google Tag Manager and Facebook and others), adding 3.3 MB and 2.4 s of main-thread time.

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

officedepot.com costs a phone 886 ms of main-thread work and 1.5 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.

Google Tag Manager costs a phone 725 ms of main-thread work and 558 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.

14 images could be 619 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.

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

Polyfills for old browsers add 202 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

Facebook costs a phone 450 ms of main-thread work and 274 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.

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

audioeye.com costs a phone 123 ms of main-thread work and 375 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.

Criteo costs a phone 45 ms of main-thread work and 396 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.

About 51 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.

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

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

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

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

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

Scripts block taps and scrolling for 4.1 s in total while the page loads. Good is under 200 ms.

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

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

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

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

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

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

Your homepage downloads 4.7 MB in 229 requests on a phone: scripts 2.7 MB (68), images 1.4 MB (63) and fonts 361 KiB (4). Under 2 MB keeps phones on slow connections fast.

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

18 tap targets are too small or too close together to hit reliably with a finger.

16 elements hidden from screen readers can still receive keyboard focus.

1 image has no alt text, which hurts accessibility and image search.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

Some list items are not inside a list.

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

Some lists contain elements other than list items, which screen readers announce wrongly.

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

Your title is 76 characters, so Google will cut it off around 60: “ODP Business Solutions | Revolutionizing Workspaces for Maximum Productivity”.

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

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

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

1 link has no real href, so search engines can't follow it.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 128 pages on odpbusiness.com and 25 external pages.

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.

There is no https://www.odpbusiness.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.

/, /;jsessionid=0000mni4ZKfQyH-MKH6OcdQ9Sza:1frd4nk8f, https://www.odpbusiness.com/orderhistory/orderHistoryList.do;jsessionid=0000mni4ZKfQyH-MKH6OcdQ9Sza:1frd4nk8f and https://www.odpbusiness.com/csl/listAll.do;jsessionid=0000mni4ZKfQyH-MKH6OcdQ9Sza:1frd4nk8f all use the title “ODP Business Solutions | Revolutionizing Workspaces for Maximum Produ…”. Search engines can't tell which page to show for a search, so each competes with the others.

/;jsessionid=0000mni4ZKfQyH-MKH6OcdQ9Sza:1frd4nk8f, https://www.odpbusiness.com/orderhistory/orderHistoryList.do;jsessionid=0000mni4ZKfQyH-MKH6OcdQ9Sza:1frd4nk8f and https://www.odpbusiness.com/csl/listAll.do;jsessionid=0000mni4ZKfQyH-MKH6OcdQ9Sza:1frd4nk8f use the same meta description. A description written for each page earns more clicks.

Your homepage links to 13 pages by a URL that isn't their canonical one, for example /;jsessionid=0000mni4ZKfQyH-MKH6OcdQ9Sza:1frd4nk8f, whose canonical is https://www.odpbusiness.com/www.odpbusiness.com. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/;jsessionid=0000mni4ZKfQyH-MKH6OcdQ9Sza:1frd4nk8f, https://www.odpbusiness.com/l/solutions-services, https://www.odpbusiness.com/l/why-odp, https://www.odpbusiness.com/l/prelogin/industry-solutions, https://www.odpbusiness.com/customerservice/help.do;jsessionid=0000mni4ZKfQyH-MKH6OcdQ9Sza:1frd4nk8f and https://www.odpbusiness.com/l/breakroom;jsessionid=0000mni4ZKfQyH-MKH6OcdQ9Sza:1frd4nk8f and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.odpbusiness.com/orderhistory/orderHistoryList.do;jsessionid=0000mni4ZKfQyH-MKH6OcdQ9Sza:1frd4nk8f and https://www.odpbusiness.com/csl/listAll.do;jsessionid=0000mni4ZKfQyH-MKH6OcdQ9Sza:1frd4nk8f have 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.

https://www.odpbusiness.com/orderhistory/orderHistoryList.do;jsessionid=0000mni4ZKfQyH-MKH6OcdQ9Sza:1frd4nk8f, https://www.odpbusiness.com/csl/listAll.do;jsessionid=0000mni4ZKfQyH-MKH6OcdQ9Sza:1frd4nk8f, https://www.odpbusiness.com/l/breakroom;jsessionid=0000mni4ZKfQyH-MKH6OcdQ9Sza:1frd4nk8f, https://www.odpbusiness.com/l/prelogin/print-services;jsessionid=0000mni4ZKfQyH-MKH6OcdQ9Sza:1frd4nk8f, https://www.odpbusiness.com/l/print-and-copy/same-day-printing;jsessionid=0000mni4ZKfQyH-MKH6OcdQ9Sza:1frd4nk8f and https://www.odpbusiness.com/l/services/tech-services;jsessionid=0000mni4ZKfQyH-MKH6OcdQ9Sza:1frd4nk8f and 1 other took over 3 s to send their HTML from our server.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

6 errors were logged to the browser console while the page loaded, for example “Identifier 'loginBtnDatalayer' has already been declared”.

Chrome logged issues while loading the page (“Cookie”).

Large scripts ship without source maps.

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

The homepage carries about 1,129 words of visible text.

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

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

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