modernshelterng.com website review

56 images could be 25.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 6.7 s faster on a phone.

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

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

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

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

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

Google Maps costs a phone 264 ms of main-thread work and 521 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 1,860 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

7 third-party services load with your homepage (Google Maps, Comodo and Cloudflare CDN and others), adding 633 KiB and 270 ms of main-thread time.

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

13 KiB could be saved by minifying CSS.

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

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.

4 KiB could be saved by minifying JavaScript.

Your largest element takes 85.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “About Us Image”.

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

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

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

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

Your homepage downloads 29.9 MB in 150 requests on a phone: images 28.7 MB (101), scripts 589 KiB (19) and fonts 419 KiB (10). Under 2 MB keeps phones on slow connections fast.

10 images weigh 22.8 MB together. On a phone connection a single image that size takes seconds.

11 images are downloaded at several times the size a phone draws them, for example b3.gif at 1,080 px wide, shown at 100 px. Resized copies would save about 19.0 MB.

40 images (25.2 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.

37 images further down the page (23.6 MB) 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 8.47 g of CO₂e: 1015.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

5 elements use ARIA attributes their role does not allow, which confuses screen readers.

Certain ARIA roles must contain particular children: 5 elements on the page fail this check, rated critical by axe-core.

ARIA attributes must conform to valid values: 5 elements on the page fail this check, rated critical by axe-core.

ARIA input fields must have an accessible name: 8 elements on the page fail this check, rated serious by axe-core.

Interactive controls must not be nested: 6 elements on the page fail this check, rated serious by axe-core.

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

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

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

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

All page content should be contained by landmarks: 16 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.

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

4 form fields have no label, so screen readers announce an empty box and autofill guesses.

The page declares lang=“zxx”, which is not a usable language code (“zxx” means “no linguistic content”), so screen readers and translation tools guess.

Elements marked as presentational should be consistently ignored: 5 elements on the page fail this check, rated minor by axe-core.

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

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

There are 39 <h1> headlines (“Affordable Housing”, “Modern Shelter Systems and Services Ltd.” and “13”). 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.

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

4 links have no real href, so search engines can't follow them.

The homepage links to 95 pages on modernshelterng.com and 13 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://modernshelterng.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.

https://modernshelterng.com/asante_Sana_2%20and%203_Bd.html, https://modernshelterng.com/asante_Sana_4Bd_villa.html, https://modernshelterng.com/asante_Sana_4Bd_Terrace.html and https://modernshelterng.com/asante_Sana_5Bd_duplex.html are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://modernshelterng.com/asante_Sana_4Bd_villa.html, https://modernshelterng.com/asante_Sana_4Bd_Terrace.html and https://modernshelterng.com/asante_Sana_5Bd_duplex.html have no meta description, so Google writes the search snippet from whatever text it finds.

https://modernshelterng.com/about.html, https://modernshelterng.com/service.html, https://modernshelterng.com/team.html, https://modernshelterng.com/mortgage.html, https://modernshelterng.com/yankari.html and https://modernshelterng.com/tinapa.html and 4 others use the same meta description. A description written for each page earns more clicks.

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

35 of 49 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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

1 image is served at too low a resolution for sharp phone screens.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

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

The homepage shows no opening hours. If customers visit or call, show when.

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

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