oslgroup.in website review

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

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

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

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

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

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

4 third-party services load with your homepage (YouTube, Other Google APIs/SDKs and Google Fonts and others), adding 1.2 MB and 502 ms of main-thread time.

YouTube costs a phone 490 ms of main-thread work and 1,013 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.

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

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

37 KiB could be saved by minifying JavaScript.

8 KiB could be saved by minifying CSS.

Polyfills for old browsers add 6 KiB JavaScript that modern phones do not need.

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 6.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

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

For real visitors the layout shifts by 0.20 (75th percentile). Good is under 0.1.

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

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

Your largest element takes 3.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Beginning its journey with stevedoring in 1978, we have gro…”. Most of its time is element render delay (6.1 s).

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

Your homepage downloads 3.0 MB in 99 requests on a phone: scripts 1.3 MB (31), images 1.0 MB (15) and fonts 331 KiB (14). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example OSL-Logo.jpeg at 848 px wide, shown at 82 px. Resized copies would save about 46 KiB.

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

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

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

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

1 image has no alt text, which hurts accessibility and image search.

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

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

Your title is only 9 characters: “OSL GROUP”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is 208 characters; Google truncates after about 160, so the end of your pitch is cut.

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

6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

Your <h1> is empty.

The homepage links to 132 pages on oslgroup.in and 16 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://oslgroup.in/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://oslgroup.in/contact-us, https://oslgroup.in/about-osl, https://oslgroup.in/stevedoring, https://oslgroup.in/empires-hotel, https://oslgroup.in/dps-kalinga and https://oslgroup.in/luxury-merchandise and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://oslgroup.in/contact-us, https://oslgroup.in/stevedoring, https://oslgroup.in/empires-hotel, https://oslgroup.in/dps-kalinga, https://oslgroup.in/luxury-merchandise and https://oslgroup.in/automobile and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://oslgroup.in/contact-us and https://oslgroup.in/dps-kalinga took over 3 s to send their HTML from our server.

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

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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 ()”.

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

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

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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.

The homepage carries about 626 words of visible text.

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