novin.com website review

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.6 s).

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

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

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

5 third-party services load with your homepage (Google Tag Manager, yektanet.com and Google/Doubleclick Ads and others), adding 548 KiB and 524 ms of main-thread time.

7 images could be 107 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

Google Tag Manager costs a phone 488 ms of main-thread work and 523 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.

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

About 55 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 230 ms faster on a phone.

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

About 205 KiB of JavaScript is downloaded but never used on this page.

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

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.

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

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

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

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

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

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

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

The layout shifts by 0.118 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Your largest element takes 2.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (2.0 s).

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

course-cover-final-2-copy.jpg weighs 804 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 3.3 MB in 114 requests on a phone: images 2.2 MB (71), scripts 607 KiB (16) and fonts 314 KiB (8). Under 2 MB keeps phones on slow connections fast.

21 images (1.5 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.

1 image is downloaded at several times the size a phone draws it, for example saeed-novin-digital-marketing.jpg at 1,280 px wide, shown at 360 px. Resized copies would save about 15 KiB.

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

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

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

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

55 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 24 elements on the page fail 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.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

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

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

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

The homepage links to 414 pages on novin.com and 7 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.

/ns-campaign is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/ns-campaign has no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /academy/start-bussines, whose canonical is /academy/start-business. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/academy has no <h1> headline, so visitors and search engines get no clear main topic.

/ns-campaign, /academy, /academy/start-bussines and /academy/youtube-bundle took over 3 s to send their HTML from our server.

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

2 errors were logged to the browser console while the page loaded, for example “jQuery is not defined”.

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

2 resources load over plain http on your https page (for example http://www.novin.com/wp-content/uploads/2025/03/text-course-cover-copy-1.jpg); browsers block or warn about them.

1 link to other sites is dead, for example https://www.aparat.com/novin.com (504).

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.

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

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

The homepage has only about 73 words of visible text; thin pages give Google and first-time buyers little to go on.

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

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

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.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 16 cookies (measured from a US location before any click).

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 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.