nalisbg.com website review

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

839 KiB could be saved by minifying JavaScript.

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

8 images could be 935 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

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

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

6 third-party services load with your homepage (Other Google APIs/SDKs, LinkedIn and Facebook and others), adding 490 KiB and 287 ms of main-thread time.

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

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

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

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

Your largest element takes 13.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Toggle navigation NALIS NALIS LTD - BRINGS INNOVATION WE AR…”.

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

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

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

3 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 are downloaded at several times the size a phone draws them, for example Tux-ea92a0ba.png at 2,000 px wide, shown at 230 px. Resized copies would save about 522 KiB.

Your homepage downloads 3.4 MB in 43 requests on a phone: scripts 1.6 MB (14), images 1.5 MB (13) and stylesheets 109 KiB (7). Under 2 MB keeps phones on slow connections fast.

3 images (692 KiB) 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.

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

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

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

3 links inside paragraphs rely on colour alone to stand out.

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

Your title is 76 characters, so Google will cut it off around 60: “Developing Ideas - Web Apps, SaaS, Software as a Service, System Integration”.

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

There are 6 <h1> headlines (“NALIS”, “Nalis Ltd - Brings Innovation” and “Services”). 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.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

There is no robots.txt at nalisbg.com/robots.txt, the first file search crawlers ask for.

The homepage links to only 1 page on your own site, so visitors and crawlers find few routes into the rest of it.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

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://nalisbg.com/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.

1 error was logged to the browser console while the page loaded, for example “Mixed Content: The page at 'https://nalisbg.com/' was loaded over HTTPS, but requested an insecure frame 'http://develo…”.

3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

Large scripts ship without source maps.

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.

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 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 389 words of visible text.

Before a visitor clicks anything, the page loads Meta Pixel (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 1 cookie, 1 of them by other companies (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 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.