369project.com website review

About 663 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.6 s faster on a phone.

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

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

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

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

8 third-party services load with your homepage (replocdn.com, cloudfront.net and Klaviyo and others), adding 2.5 MB and 1.2 s of main-thread time.

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

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

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

replocdn.com costs a phone 497 ms of main-thread work and 407 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 228 ms of main-thread work and 459 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.

Klaviyo costs a phone 180 ms of main-thread work and 329 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.

Shopify costs a phone 74 ms of main-thread work and 1.2 MB 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.

59 KiB could be saved by minifying JavaScript.

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

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

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

Desktop scores 63 but mobile only 33. A gap that wide usually means heavy scripts and images that hit phones hardest.

9 KiB could be saved by minifying CSS.

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.

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

Your largest element takes 18.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “500,000+ COPIES SOLD AWAKEN TO WHO YOU TRULY ARE AND MANIFE…”.

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

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

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

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

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

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

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.

Your homepage downloads 4.1 MB in 307 requests on a phone: scripts 1.8 MB (103), images 967 KiB (34) and other files 794 KiB (115). Under 2 MB keeps phones on slow connections fast.

Project_369-Book_Combo_2_1.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).

3 images are downloaded at several times the size a phone draws them, for example CopyofCopyofJournalmockupsforYoutube_7_beb819d0-3b74-47e6-8b at 820 px wide, shown at 148 px. Resized copies would save about 207 KiB.

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

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

6 tap targets are too small or too close together to hit reliably with a finger.

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

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 → h6), which makes the page harder to scan with a screen reader.

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 22 characters: “Higher Mind Publishing”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 4 <h1> headlines (“”, “400,000+ Manifesters” and “you’re about to learn the”). One clear main headline is easier for people and search engines.

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

The homepage links to 38 pages on 369project.com and 8 external pages.

/customer_authentication/redirect has no <title>, so Google invents the link text in results.

/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/collections/all, /customer_authentication/redirect, /pages/meditations, /blogs/manifestation-tips and /collections/project-369-books have no meta description, so Google writes the search snippet from whatever text it finds.

/products/369-manifestation-journal and /products/project-369-the-key-to-the-universe-evolved-consciousness-scripture-edition use the same meta description. A description written for each page earns more clicks.

/collections/all, /customer_authentication/redirect, /products/the-ultimate-manifestation-bundle, /products/project-369-manifestation-planner, /products/project-369-the-key-to-wholeness-soul-work-journal and /products/the-prayer-journal-a-33-day-journey-into-the-kingdom-within and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 14 pages linked from your homepage and read each the way a search engine does.

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

5 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'id')”.

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

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

1 link go through two or more redirects, for example https://369project.com/customer_authentication/redirect?locale=en&region_country=US.

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.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

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

369project.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.

369project.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 1,918 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

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

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, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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 18 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 33 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.