icanotes.com website review

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

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

About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.

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

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

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

8 third-party services load with your homepage (reddit, cloudfront.net and Google CDN and others), adding 1.8 MB and 2.5 s of main-thread time.

reddit costs a phone 824 ms of main-thread work and 26 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 165 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

Google CDN costs a phone 365 ms of main-thread work and 733 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.

cloudfront.net costs a phone 384 ms of main-thread work and 508 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.

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

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

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

38 KiB could be saved by minifying JavaScript.

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

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.

Your largest element takes 13.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Complete notes in under 3 minutes with template-driven effi…”.

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

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

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

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

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

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

Your homepage downloads 4.2 MB in 273 requests on a phone: scripts 2.9 MB (88), other files 438 KiB (96) and fonts 367 KiB (9). Under 2 MB keeps phones on slow connections fast.

1 image (45 KiB) is 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.

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

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

1 frame has no title, so screen-reader users cannot tell what it contains.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

6 links have no real href, so search engines can't follow them.

The homepage links to 196 pages on icanotes.com and 9 external pages.

/support-hub and /knowledge-base-hub have no meta description, so Google writes the search snippet from whatever text it finds.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=27025428&tm=gtm002&Ver=2&mid=d04ddc5f-d0fe-41a4-84ed-becdc808b2cc&bo=1&sid=5ade11f0cbd711f1ba3b47cdd6fe8145&vid=5ade1510cbd711f19e43b700d2fafdfe&vids=1&msclkid=N&pi=91.

3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

Large scripts ship without source maps.

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

icanotes.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

icanotes.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 2,332 words of visible text.

DMARC is set to p=none, so mail pretending to be icanotes.com is still delivered. Add a report address, check the reports, then move to quarantine.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, HubSpot, LinkedIn Insight and Meta Pixel and 4 mores (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 47 cookies, 1 of them by other companies (measured from a US location before any click).

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