Website review, no card needed
oceanstatejoblot.com website review
Visit site (opens in a new tab)Reviewed 12 October 202651 issues · 95 checks
This review found 51 issues worth fixing on oceanstatejoblot.com, 22 of them high impact, across 95 checks. The most urgent: reduce unused JavaScript. 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
60DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 18, 2026 | 2.5 s |
| Apr 25, 2026 | 2.5 s |
| May 2, 2026 | 2.6 s |
| May 9, 2026 | 2.6 s |
| May 16, 2026 | 2.6 s |
| May 23, 2026 | 2.7 s |
| May 30, 2026 | 2.7 s |
| Jun 6, 2026 | 2.7 s |
| Jun 13, 2026 | 2.6 s |
| Jun 20, 2026 | 2.6 s |
| Jun 27, 2026 | 2.6 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.6 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.6 s |
| Aug 8, 2026 | 2.6 s |
| Aug 15, 2026 | 2.7 s |
| Aug 22, 2026 | 2.7 s |
| Aug 29, 2026 | 2.7 s |
| Sep 5, 2026 | 2.7 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.6 s |
| Oct 3, 2026 | 2.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 18, 2026 | 156 ms |
| Apr 25, 2026 | 160 ms |
| May 2, 2026 | 162 ms |
| May 9, 2026 | 162 ms |
| May 16, 2026 | 161 ms |
| May 23, 2026 | 158 ms |
| May 30, 2026 | 155 ms |
| Jun 6, 2026 | 157 ms |
| Jun 13, 2026 | 159 ms |
| Jun 20, 2026 | 160 ms |
| Jun 27, 2026 | 162 ms |
| Jul 4, 2026 | 163 ms |
| Jul 11, 2026 | 166 ms |
| Jul 18, 2026 | 168 ms |
| Jul 25, 2026 | 167 ms |
| Aug 1, 2026 | 166 ms |
| Aug 8, 2026 | 169 ms |
| Aug 15, 2026 | 171 ms |
| Aug 22, 2026 | 175 ms |
| Aug 29, 2026 | 179 ms |
| Sep 5, 2026 | 180 ms |
| Sep 12, 2026 | 179 ms |
| Sep 19, 2026 | 179 ms |
| Sep 26, 2026 | 178 ms |
| Oct 3, 2026 | 176 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.5 s
2.0 s
2.5 s
3.1 s
3.6 s
4.1 s
Speed
Reduce unused JavaScript
4.3 s · 758 KiBAbout 758 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.3 s faster on a phone.
Use efficient cache lifetimes
2.9 s · 1.1 MB125 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).
Render-blocking requests
1.9 s15 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Minify JavaScript
1.2 s · 158 KiB158 KiB could be saved by minifying JavaScript.
Mobile performance score: 23
23/100Your mobile performance score is 23 (desktop: 29). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
9,901 HTML elements
The page has 9,901 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 5.7 s
A phone's processor spends 5.7 s on main-thread work while loading, 3.1 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 (Google Tag Manager, Noibu and mozu.com and others), adding 7.1 MB and 2.6 s of main-thread time.
Improve image delivery
2.8 MB31 images could be 2.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
mozu.com adds 509 ms
509 msmozu.com costs a phone 509 ms of main-thread work and 5.7 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.
Reduce unused CSS
770 ms · 130 KiBAbout 130 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 770 ms faster on a phone.
Google Tag Manager adds 712 ms
712 msGoogle Tag Manager costs a phone 712 ms of main-thread work and 815 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.
Noibu adds 620 ms
620 msNoibu costs a phone 620 ms of main-thread work and 114 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.
Legacy JavaScript
450 ms · 66 KiBPolyfills for old browsers add 66 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.
Facebook adds 332 ms
332 msFacebook costs a phone 332 ms of main-thread work and 279 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.
Minify CSS
300 ms · 57 KiB57 KiB could be saved by minifying CSS.
19 long tasks on the main thread
19 long tasks block the main thread while loading, the longest for 329 ms. During a long task the page ignores taps.
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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 11 ms
11 msYour server sent the HTML in 11 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.
Largest Contentful Paint: 28.4 s
28.4 sYour largest element takes 28.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Get 40% Back! Insider Crazy Deal Days. Spend $30.00 or more…”.
Time to Interactive: 29.1 s
29.1 sThe page becomes fully interactive after 29.1 s. Good is under 3.8 s.
Speed Index: 13.2 s
13.2 sVisually, the page fills in at 13.2 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 5.2 s
5.2 sThe first text or image appears after 5.2 s on a phone. Good is under 1.8 s.
Total Blocking Time: 1.2 s
1.2 sScripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.0 s
3.0 sReal visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.23
0.23For real visitors the layout shifts by 0.23 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.206
0.206The layout shifts by 0.206 while loading, so content jumps under the reader's thumb. Good is under 0.1.
31 images without width and height
31 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 156 ms to 176 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 2.5 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 194 ms
194 msReal visitors wait 194 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 535 ms
535 msReal visitors wait 535 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 7.6 MB in 210 requests
7.6 MBYour homepage downloads 7.6 MB in 210 requests on a phone: images 4.6 MB (88), scripts 2.2 MB (52) and fonts 484 KiB (9). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
0a4e840b-96d6-4f53-8970-f8b4896533a0 weighs 1.4 MB. On a phone connection a single image that size takes seconds.
4 images far larger than shown
1.6 MB4 images are downloaded at several times the size a phone draws them, for example 0a4e840b-96d6-4f53-8970-f8b4896533a0 at 2,048 px wide, shown at 110 px. Resized copies would save about 1.6 MB.
14 images in older formats
14 images (2.3 MB) 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.
11 images below the first screen load straight away
11 images further down the page (484 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.1 g of CO₂ per visit
2.14 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.14 g of CO₂e: 257.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Hidden but focusable
2 elements hidden from screen readers can still receive keyboard focus.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
Banner landmark should not be contained in another landmark (7 elements)
Banner landmark should not be contained in another landmark: 7 elements on the page fail this check, rated moderate 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.
Users should be able to zoom and scale the text up to 500% (1 element)
Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (4 elements).
1 checks passed
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
18 links crawlers can't follow
18 links have no real href, so search engines can't follow them.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
1,206 internal links, 23 external
The homepage links to 1,206 pages on oceanstatejoblot.com and 23 external pages.
6 checks passed
Meta description: 159 characters
Your meta description is 159 characters: “Shop Ocean State Job Lot online and in-store for everything from household essentials to clothing and electronics. Ship…”.
One H1 headline
Your main headline reads: “Ocean State Job Lot Homepage”.
Title: 59 characters
Your title is a healthy 59 characters: “Ocean State Job Lot - Shop great deals on name brand items!”.
Canonical URL set
The canonical URL is https://www.oceanstatejoblot.com/.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.oceanstatejoblot.com/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.oceanstatejoblot.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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (4,603 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page with very little text
https://www.oceanstatejoblot.com/store-locator 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 197 found) and read each the way a search engine does.
7 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 1 page that loaded have a meta description.
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 1 page that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97173684&Ver=2&mid=5340d177-2685-4343-b95b-aebb948a140d&bo=1&sid=e4f67840c5cf11f1b759e7317f5907c6&vid=e4f689e0c5cf11f1a1c7d78a25ccd085&vids=1&msclkid=N&pi=918639831&lg.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://osjl.blueconic.net/DG/DEFAULT/rest/rpc/179?referer=https%3A%2F%2Fwww.oceanstatejob…”.
2 checks passed
Tap targets are thumb-sized
46 of 54 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
A 8-field form
Your longest form asks for 8 fields (0 required). Every extra field lowers completion.
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 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 1,208 words of copy
The homepage carries about 1,208 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: “Login or Register” and “Buy Online”.
25 calls to action
The homepage has 25 calls to action, for example “Send Request”, “Christmas Shop” and “Buy Online”.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 2 mores (measured from a US location before any click). A consent tool (TrustArc) is installed; check it blocks these until visitors agree where the law requires it.
23 cookies set on arrival
23Opening the homepage sets 23 cookies, 3 of them by other companies (measured from a US location before any click).
41 other companies contacted
Loading the homepage contacts 41 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: TrustArc
A consent management tool (TrustArc) 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 oceanstatejoblot.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 51 issues on oceanstatejoblot.com, including 27 speed issues, 5 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.