Website review, no card needed

evernote.com logo

evernote.com website review

Visit site (opens in a new tab)Reviewed 2 November 202639 issues · 88 checks

This review found 39 issues worth fixing on evernote.com, 12 of them high impact, across 88 checks. The most urgent: use efficient cache lifetimes. 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

Real-visitor load time (LCP)75th percentile, phones
2.8 s2.2 sMay 16Oct 312.5 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.7 s
May 23, 20262.7 s
May 30, 20262.7 s
Jun 6, 20262.7 s
Jun 13, 20262.7 s
Jun 20, 20262.6 s
Jun 27, 20262.6 s
Jul 4, 20262.6 s
Jul 11, 20262.5 s
Jul 18, 20262.4 s
Jul 25, 20262.3 s
Aug 1, 20262.3 s
Aug 8, 20262.3 s
Aug 15, 20262.3 s
Aug 22, 20262.3 s
Aug 29, 20262.3 s
Sep 5, 20262.3 s
Sep 12, 20262.3 s
Sep 19, 20262.4 s
Sep 26, 20262.3 s
Oct 3, 20262.3 s
Oct 10, 20262.3 s
Oct 17, 20262.4 s
Oct 24, 20262.5 s
Oct 31, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
400 ms281 msMay 16Oct 31386 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026328 ms
May 23, 2026338 ms
May 30, 2026338 ms
Jun 6, 2026339 ms
Jun 13, 2026338 ms
Jun 20, 2026338 ms
Jun 27, 2026340 ms
Jul 4, 2026343 ms
Jul 11, 2026344 ms
Jul 18, 2026342 ms
Jul 25, 2026338 ms
Aug 1, 2026332 ms
Aug 8, 2026325 ms
Aug 15, 2026316 ms
Aug 22, 2026309 ms
Aug 29, 2026302 ms
Sep 5, 2026300 ms
Sep 12, 2026296 ms
Sep 19, 2026295 ms
Sep 26, 2026305 ms
Oct 3, 2026324 ms
Oct 10, 2026346 ms
Oct 17, 2026373 ms
Oct 24, 2026385 ms
Oct 31, 2026386 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

Full-page screenshot of evernote.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

9 to fix52
  • Use efficient cache lifetimes

    2.6 s · 2.2 MB

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

  • 3,003 HTML elements

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

  • Mobile performance score: 52

    52/100

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

  • Render-blocking requests

    700 ms

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.

  • Reduce unused JavaScript

    300 ms · 200 KiB

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

  • 8 long tasks on the main thread

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

  • Main-thread work: 2.6 s

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

  • Improve image delivery

    253 KiB

    5 images could be 253 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • prismic.io adds 4 ms

    4 ms

    prismic.io costs a phone 4 ms of main-thread work and 359 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.

  • Document request latency

    249 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • 6 third-party services on the page

    6 third-party services load with your homepage (hcaptcha.com, Optanon and prismic.io and others), adding 721 KiB and 126 ms of main-thread time.

  • Reduce unused CSS

    150 ms · 48 KiB

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

  • Legacy JavaScript

    35 KiB

    Polyfills for old browsers add 35 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.

1 checks passed
  • Server response: 97 ms

    97 ms

    Your server sent the HTML in 97 ms, well inside Google's 600 ms guideline.

Core Web Vitals

9 to fix67
  • 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.

  • Time to Interactive: 21.7 s

    21.7 s

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

  • Largest Contentful Paint: 7.8 s

    7.8 s

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

  • Total Blocking Time: 644 ms

    644 ms

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

  • Real-user LCP: 2.8 s

    2.8 s

    Real visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user FCP: 2.1 s

    2.1 s

    Real visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 1.5 s

    1.5 s

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • Speed Index: 4.4 s

    4.4 s

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

  • Tap response (INP) got 16% slower for real visitors

    +16%

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

  • Largest content (LCP) held steady for real visitors

    -7%

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

3 checks passed
  • Real-user INP: 196 ms

    196 ms

    Real visitors wait 196 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix81
  • Page weight: 3.7 MB in 99 requests

    3.7 MB

    Your homepage downloads 3.7 MB in 99 requests on a phone: scripts 2.6 MB (48), images 468 KiB (28) and HTML 374 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    aOULcZ5xUNkB1rwQ_hero-mobile-hp.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).

  • About 1.0 g of CO₂ per visit

    1.04 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

10 to fixGoogle 6685
  • 1 button without a name

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

  • Hidden but focusable

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

  • 5 text elements with low contrast

    5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • Malformed lists

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 5 links without text

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

  • Elements use prohibited ARIA attributes

    Elements use prohibited ARIA attributes (2 elements).

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Headings skip levels

    Headings skip levels (h2 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 63 images in the HTML carry an alt attribute.

  • 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. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10097
  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 115 internal links, 26 external

    The homepage links to 115 pages on evernote.com and 26 external pages.

7 checks passed
  • Meta description: 151 characters

    Your meta description is 151 characters: “Our note taking app helps you capture and prioritize ideas, projects and to-do lists, so nothing falls through the crac…”.

  • One H1 headline

    Your main headline reads: “Your second brain”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “Best Note Taking App - Organize Your Notes with Evernote”.

  • Canonical URL set

    The canonical URL is https://evernote.com/.

  • Structured data in place

    Structured data found: Organization.

  • 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://evernote.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 (681 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://evernote.com/llms.txt (12 KiB, 80 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix76
  • 1 page points its canonical at the homepage

    https://evernote.com/en-us declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 3 pages share a title

    /, https://evernote.com/en-us and https://evernote.com/en-us/features/notes-app all use the title “Best Note Taking App - Organize Your Notes with Evernote”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages share a meta description

    https://evernote.com/en-us, https://evernote.com/en-us/features/ai-features and https://evernote.com/en-us/features/collaboration use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://evernote.com/en-us/features/ai-features has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://evernote.com/ai-rewrite 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 40 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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 to fixGoogle 8197
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“The Protected Audience API is deprecated and will be removed in a future release.”).

  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    29 of 30 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix70
  • Thin social proof

    Social proof on the homepage: 3 trust badges. 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.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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 560 words of copy

    The homepage carries about 560 words of visible text.

2 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Download”.

  • 13 calls to action

    The homepage has 13 calls to action, for example “Download”, “Start for free” and “Try it for free”.

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

  • 7 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 evernote.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
Google Cloud

Company

Founded
2008

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on evernote.com, including 18 speed issues, 1 SEO issue 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

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