ipublisher.net website review

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

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

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

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

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

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

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

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

1 third-party service load with your homepage (Google Fonts), adding 50 KiB and 0 ms of main-thread time.

Your largest element takes 11.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “SDS Authoring has never been simpler| iPublisher is a globa…”.

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

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

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

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

2 images weigh 1.4 MB together. On a phone connection a single image that size takes seconds.

Your homepage downloads 3.8 MB in 61 requests on a phone: images 3.2 MB (43), scripts 259 KiB (9) and stylesheets 212 KiB (4). Under 2 MB keeps phones on slow connections fast.

4 images further down the page (2.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

2 images (1.1 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.

2 images are downloaded at several times the size a phone draws them, for example publish-img-1.png at 1,495 px wide, shown at 341 px. Resized copies would save about 430 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 1.09 g of CO₂e: 130.4 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”.

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

All page content should be contained by landmarks: 17 elements on the page fail this check, rated moderate by axe-core.

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

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

The robots meta tag says “noindex”: Google is told not to list this page at all.

Google's crawler is blocked from indexing this page.

Your title is 88 characters, so Google will cut it off around 60: “iPublisher - SaaS solution for creating, publishing, and distributing Safety Data Sheets”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 2 <h1> headlines (“SDS Authoring has never been easier” and “Fully loaded with the best features”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

1 link has no real href, so search engines can't follow it.

The homepage links to 10 pages on ipublisher.net and 0 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 https://ipublisher.net/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.

https://ipublisher.net/Privacy and https://ipublisher.net/Contact are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://ipublisher.net/Privacy and https://ipublisher.net/Contact use the same meta description. A description written for each page earns more clicks.

https://ipublisher.net/Privacy and https://ipublisher.net/Contact have no <h1> headline, so visitors and search engines get no clear main topic.

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

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.

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

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

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

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.