notifystudio.com website review

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

ai.in costs a phone 17 ms of main-thread work and 306 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 131 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

1 image could be 101 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

12 files are served with short cache lifetimes, so returning visitors download them again (92 KiB).

1 long task block the main thread while loading, the longest for 65 ms. During a long task the page ignores taps.

3 third-party services load with your homepage (ai.in, webdatastudio.com and ably.com), adding 372 KiB and 17 ms of main-thread time.

About 31 KiB of CSS is downloaded but never applied on this page.

11 KiB could be saved by minifying JavaScript.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

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

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

2 images have no width and height attributes, so the layout jumps as each one loads.

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

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

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Your title is 74 characters, so Google will cut it off around 60: “NotifyStudio | Website Engagement, Notification Widgets & Conversion Tools”.

Structured data found (SoftwareApplication) but with 1 problem, for example “SoftwareApplication: no offers (price) block”.

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

No XML sitemap at https://notifystudio.com/sitemap.xml, so Google discovers your pages only by following links.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

The homepage links to 53 pages on notifystudio.com and 4 external pages.

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.

There is no /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.

/solutions/for-ecommerce-stores, /features/informational-messages, /features/coupons-and-promotions, /features/social-proof-and-conversions, /features/popup-collectors and /features/multimedia-engagement and 1 other declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

/features, /services and /products all use the title “Features — NotifyStudio | Popup Widgets, Social Proof & Conversion To…”. Search engines can't tell which page to show for a search, so each competes with the others.

/features, /services and /products use the same meta description. A description written for each page earns more clicks.

/use-cases, /features/coupons-and-promotions, /features/social-proof-and-conversions, /features/multimedia-engagement and /features/feedback-and-interactions have no <h1> headline, so visitors and search engines get no clear main topic.

/integrations and /resources/insights 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.

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

Does not redirect HTTP traffic to HTTPS.

Your homepage is served without HTTPS, so browsers mark it “Not secure” and some refuse forms on it.

http://notifystudio.com does not redirect to https, so some visitors land on the insecure version.

3 links go through two or more redirects, for example http://notifystudio.com/contact/.

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

notifystudio.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.

notifystudio.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.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 645 words of visible text.

notifystudio.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

Your SPF record doesn't end in -all or ~all, so it doesn't stop other servers sending as you: “v=spf1 redirect=_spf.mailhostbox.com”.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

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.

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.

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