Website review, no card needed
remarkable.com website review
Visit site (opens in a new tab)Reviewed 4 November 202617 issues · 55 checks
This review found 17 issues worth fixing on remarkable.com, 3 of them high impact, across 55 checks. The most urgent: fails Core Web Vitals for real visitors. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. 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
Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.
Show as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.4 s |
| May 23, 2026 | 2.7 s |
| May 30, 2026 | 2.9 s |
| Jun 6, 2026 | 3.2 s |
| Jun 13, 2026 | 3.4 s |
| Jun 20, 2026 | 3.4 s |
| Jun 27, 2026 | 3.3 s |
| Jul 4, 2026 | 3.1 s |
| Jul 11, 2026 | 2.8 s |
| Jul 18, 2026 | 2.6 s |
| Jul 25, 2026 | 2.3 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.3 s |
| Sep 5, 2026 | 2.3 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.4 s |
| Oct 24, 2026 | 2.4 s |
| Oct 31, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 245 ms |
| May 23, 2026 | 257 ms |
| May 30, 2026 | 271 ms |
| Jun 6, 2026 | 297 ms |
| Jun 13, 2026 | 302 ms |
| Jun 20, 2026 | 304 ms |
| Jun 27, 2026 | 301 ms |
| Jul 4, 2026 | 292 ms |
| Jul 11, 2026 | 286 ms |
| Jul 18, 2026 | 279 ms |
| Jul 25, 2026 | 270 ms |
| Aug 1, 2026 | 264 ms |
| Aug 8, 2026 | 263 ms |
| Aug 15, 2026 | 260 ms |
| Aug 22, 2026 | 260 ms |
| Aug 29, 2026 | 256 ms |
| Sep 5, 2026 | 254 ms |
| Sep 12, 2026 | 254 ms |
| Sep 19, 2026 | 253 ms |
| Sep 26, 2026 | 256 ms |
| Oct 3, 2026 | 260 ms |
| Oct 10, 2026 | 260 ms |
| Oct 17, 2026 | 263 ms |
| Oct 24, 2026 | 262 ms |
| Oct 31, 2026 | 256 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
Speed
Not measured in this review.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user INP: 255 ms
255 msReal visitors wait 255 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 245 ms to 256 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.09
0.09For real visitors the layout shifts by 0.09 (75th percentile). Good is under 0.1.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 429 ms
429 msReal visitors wait 429 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 4.5 MB
4.5 MBYour homepage downloads 4.5 MB on a phone, 65 KiB of it images (1%). Under 2 MB keeps phones on slow connections fast.
About 1.3 g of CO₂ per visit
1.27 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.27 g of CO₂e: 152.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
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
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.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 82 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 1 failed. 4 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.
2 H1 headlines
There are 2 <h1> headlines (“reMarkable does not ship to your current location…” and “The gift of all your notes in one place”). One clear main headline is easier for people and search engines.
34 internal links, 12 external
The homepage links to 34 pages on remarkable.com and 12 external pages.
6 checks passed
Meta description: 102 characters
Your meta description is 102 characters: “reMarkable - "Replace your notes and printed documents with a digital notebook that feels like paper."”.
Title: 59 characters
Your title is a healthy 59 characters: “reMarkable: The Paper Tablets for Focused Work | reMarkable”.
Canonical URL set
The canonical URL is https://remarkable.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 and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://remarkable.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.
3 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 (815 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://remarkable.com/llms.txt (7 KiB, 13 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.
Other pages
8 pages share 3 titles
https://remarkable.com/shop/all/remarkable-paper-pure and https://remarkable.com/shop/all/remarkable-paper-pro all use the title “All products | reMarkable”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
6 pages without a meta description
https://remarkable.com/shop/all/remarkable-paper-pure, https://remarkable.com/shop/all/remarkable-paper-pro, https://remarkable.com/shop, https://remarkable.com/products/remarkable-paper/pure, https://remarkable.com/products/remarkable-paper/pro-move and https://remarkable.com/products/remarkable-paper/pro have no meta description, so Google writes the search snippet from whatever text it finds.
9 pages share a meta description
https://remarkable.com/business, https://remarkable.com/why-choose-remarkable, https://remarkable.com/ways-to-use, https://remarkable.com/professional-workflows, https://remarkable.com/who-its-for and https://remarkable.com/who-its-for-lawyers and 3 others use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 26 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.
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 15 pages that loaded have a <title>.
Best practices
2 broken images
2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=5947138&tm=gtm002&Ver=2&mid=0f3a37a2-69c7-48fc-884e-92910b0b95b0&bo=1&sid=90790af0d88d11f1a06e6bd49373ea8f&vid=90793a50d88d11f1ba9bb55923c42b44&vids=1&msclkid=N&pi=918.
2 small tap targets
2 of 8 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Minified React error #418; visit https://react.dev/errors/418?args[]=HTML&args[]= for the full message or use the non-m…”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 3 testimonial or review blocks. 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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
About 495 words of copy
The homepage carries about 495 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop products”.
10 calls to action
The homepage has 10 calls to action, for example “Sign up”, “Shop” and “Shop products”.
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
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
15 trackers load before any consent
15Before a visitor clicks anything, the page loads Amplitude, Google Ads, Google Tag Manager, Hotjar and HubSpot and 10 mores (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.
42 cookies set on arrival
42Opening the homepage sets 42 cookies (measured from a US location before any click).
56 other companies contacted
Loading the homepage contacts 56 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 remarkable.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
- Next.js
- Hosting
- Vercel
Company
- Employees
- 229
- Founded
- 2013
- Headquarters
- Oslo
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 17 issues on remarkable.com, including 2 speed issues, 2 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.