Website review, no card needed
officemax.com.mx website review
Visit site (opens in a new tab)Reviewed 26 October 202650 issues · 93 checks
This review found 50 issues worth fixing on officemax.com.mx, 25 of them high impact, across 93 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
64DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.4 s |
| May 16, 2026 | 3.4 s |
| May 23, 2026 | 3.3 s |
| May 30, 2026 | 3.2 s |
| Jun 6, 2026 | 3.2 s |
| Jun 13, 2026 | 3.2 s |
| Jun 20, 2026 | 3.3 s |
| Jun 27, 2026 | 3.4 s |
| Jul 4, 2026 | 3.5 s |
| Jul 11, 2026 | 3.5 s |
| Jul 18, 2026 | 3.5 s |
| Jul 25, 2026 | 3.5 s |
| Aug 1, 2026 | 3.5 s |
| Aug 8, 2026 | 3.4 s |
| Aug 15, 2026 | 3.4 s |
| Aug 22, 2026 | 3.3 s |
| Aug 29, 2026 | 3.3 s |
| Sep 5, 2026 | 3.3 s |
| Sep 12, 2026 | 3.3 s |
| Sep 19, 2026 | 3.3 s |
| Sep 26, 2026 | 3.3 s |
| Oct 3, 2026 | 3.3 s |
| Oct 10, 2026 | 3.3 s |
| Oct 17, 2026 | 3.4 s |
| Oct 24, 2026 | 3.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 299 ms |
| May 16, 2026 | 298 ms |
| May 23, 2026 | 300 ms |
| May 30, 2026 | 301 ms |
| Jun 6, 2026 | 313 ms |
| Jun 13, 2026 | 322 ms |
| Jun 20, 2026 | 332 ms |
| Jun 27, 2026 | 347 ms |
| Jul 4, 2026 | 353 ms |
| Jul 11, 2026 | 353 ms |
| Jul 18, 2026 | 347 ms |
| Jul 25, 2026 | 339 ms |
| Aug 1, 2026 | 333 ms |
| Aug 8, 2026 | 330 ms |
| Aug 15, 2026 | 331 ms |
| Aug 22, 2026 | 330 ms |
| Aug 29, 2026 | 330 ms |
| Sep 5, 2026 | 337 ms |
| Sep 12, 2026 | 341 ms |
| Sep 19, 2026 | 341 ms |
| Sep 26, 2026 | 341 ms |
| Oct 3, 2026 | 335 ms |
| Oct 10, 2026 | 324 ms |
| Oct 17, 2026 | 328 ms |
| Oct 24, 2026 | 333 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
How it loaded on a phone
0.5 s
1.0 s
1.6 s
2.1 s
2.6 s
3.1 s
3.7 s
4.2 s
Speed
Render-blocking requests
7.3 s38 files block the first paint until they finish downloading. Deferring or inlining them could save about 7.3 s.
Reduce unused JavaScript
5.5 s · 903 KiBAbout 903 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.5 s faster on a phone.
Use efficient cache lifetimes
2.4 s · 698 KiB38 files are served with short cache lifetimes, so returning visitors download them again (698 KiB).
Improve image delivery
1.9 s · 286 KiB4 images could be 286 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.
Mobile performance score: 38
38/100Your mobile performance score is 38 (desktop: 53). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
5,464 HTML elements
The page has 5,464 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 4.2 s
A phone's processor spends 4.2 s on main-thread work while loading, 2.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (vtexassets.com, Google Tag Manager and Google CDN and others), adding 3.9 MB and 1.5 s of main-thread time.
Reduce unused CSS
610 ms · 134 KiBAbout 134 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 610 ms faster on a phone.
vtexassets.com adds 489 ms
489 msvtexassets.com costs a phone 489 ms of main-thread work and 1.9 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 adds 390 ms
390 msGoogle Tag Manager costs a phone 390 ms of main-thread work and 533 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.
Google CDN adds 243 ms
243 msGoogle CDN costs a phone 243 ms of main-thread work and 743 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.
17 long tasks on the main thread
17 long tasks block the main thread while loading, the longest for 299 ms. During a long task the page ignores taps.
Legacy JavaScript
200 ms · 85 KiBPolyfills for old browsers add 85 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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.
Minify JavaScript
4 KiB4 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 42 ms
42 msYour server sent the HTML in 42 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Real-user CLS: 0.33
0.33For real visitors the layout shifts by 0.33 (75th percentile). Good is under 0.1.
First Contentful Paint: 15.4 s
15.4 sThe first text or image appears after 15.4 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 25.3 s
25.3 sYour largest element takes 25.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Muebles de oficina con hasta 50% de descuento en OfficeMax”.
Speed Index: 15.4 s
15.4 sVisually, the page fills in at 15.4 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 30.4 s
30.4 sThe page becomes fully interactive after 30.4 s. Good is under 3.8 s.
Total Blocking Time: 701 ms
701 msScripts block taps and scrolling for 701 ms in total while the page loads. Good is under 200 ms.
Real-user INP: 287 ms
287 msReal visitors wait 287 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.4 s
2.4 sReal visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.0 s
1.0 sReal visitors wait 1.0 s for your server to start answering (75th percentile). Good is under 800 ms.
20 images without width and height
20 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 299 ms to 333 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.4 s to 3.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.1 MB in 188 requests
5.1 MBYour homepage downloads 5.1 MB in 188 requests on a phone: scripts 2.7 MB (61), other files 737 KiB (48) and fonts 718 KiB (5). Under 2 MB keeps phones on slow connections fast.
4 images in older formats
4 images (338 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 1.4 g of CO₂ per visit
1.44 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.44 g of CO₂e: 172.5 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
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
7 tap targets too small
7 tap targets are too small or too close together to hit reliably with a finger.
Hidden but focusable
3 elements hidden from screen readers can still receive keyboard focus.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
Orphan list items
Some list items are not inside a list.
18 images without alt text
18 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
No main landmark
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)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
39 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Structured data has 1 problem
Structured data found (ItemList and WebSite) but with 1 problem, for example “WebSite: missing name”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
50 internal links, 12 external
The homepage links to 50 pages on officemax.com.mx and 12 external pages.
5 checks passed
Meta description: 147 characters
Your meta description is 147 characters: “Compra en OfficeMax México: suministros de oficina, tecnología, escolares y más con envío rápido. ¡Las mejores marcas, …”.
Title: 58 characters
Your title is a healthy 58 characters: “OfficeMax | Arte, Papelería, Artículos Escolares y Muebles”.
Canonical URL set
The canonical URL is https://www.officemax.com.mx/.
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.officemax.com.mx/sitemap.xml.
AI search readiness
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.
No llms.txt
There is no https://www.officemax.com.mx/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.
1 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.
Other pages
8 pages share a meta description
https://www.officemax.com.mx/computo, https://www.officemax.com.mx/impresion, https://www.officemax.com.mx/electronica, https://www.officemax.com.mx/articulos-de-oficina, https://www.officemax.com.mx/articulos-escolares and https://www.officemax.com.mx/libros and 2 others use the same meta description. A description written for each page earns more clicks.
15 pages without an H1
https://www.officemax.com.mx/muebles, https://www.officemax.com.mx/computo, https://www.officemax.com.mx/impresion, https://www.officemax.com.mx/electronica, https://www.officemax.com.mx/papel and https://www.officemax.com.mx/articulos-de-oficina and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 pages with very little text
https://www.officemax.com.mx/muebles, https://www.officemax.com.mx/computo, https://www.officemax.com.mx/impresion, https://www.officemax.com.mx/electronica, https://www.officemax.com.mx/papel and https://www.officemax.com.mx/articulos-de-oficina and 9 others 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.
7 pages slow to respond
https://www.officemax.com.mx/impresion, https://www.officemax.com.mx/arte-y-diseno, https://www.officemax.com.mx/libros, https://www.officemax.com.mx/mochilas-y-bolsas, https://www.officemax.com.mx/belleza-y-cuidado-personal and https://www.officemax.com.mx/contenedores-y-almacenamiento and 1 other took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 35 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.
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 broken image
1 image failed to load on a phone, for example https://www.officemax.com.mx/.
17 small tap targets
17 of 41 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 “Cannot read properties of undefined (reading 'register')”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
Local business without LocalBusiness data
Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
Only about 117 words
The homepage has only about 117 words of visible text; thin pages give Google and first-time buyers little to go on.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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.
5 checks passed
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 18 testimonial or review blocks and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager and Meta Pixel.
Direct contact links
Visitors can reach you directly: 1 phone link 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
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 1 more (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.
22 cookies set on arrival
22Opening the homepage sets 22 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.
35 other companies contacted
Loading the homepage contacts 35 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 officemax.com.mx, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager | LogRocket
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 50 issues on officemax.com.mx, including 24 speed issues, 3 SEO issues and 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.