otsmanetwork.com website review

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

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

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

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

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

8 third-party services load with your homepage (Shopify, loox.io and Cloudflare CDN and others), adding 515 KiB and 290 ms of main-thread time.

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

Polyfills for old browsers add 17 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.

2 KiB could be saved by minifying JavaScript.

Your largest element takes 5.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Otsmanetwork”.

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

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

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

1 image 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 2.1 MB in 192 requests on a phone: other files 1,022 KiB (108), scripts 717 KiB (56) and fonts 201 KiB (6). Under 2 MB keeps phones on slow connections fast.

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

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

8 elements hidden from screen readers can still receive keyboard focus.

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Headings skip levels (h1 → h4), 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.

Structured data found (Organization and WebSite) but with 5 problems, for example “Organization: sameAs is not an absolute URL ("#")”.

The homepage links to 59 pages on otsmanetwork.com and 1 external page.

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

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

https://otsmanetwork.com/collections/%D8%B4%D9%88%D8%A8%D9%8A%D9%81%D8%A7%D9%8A, https://otsmanetwork.com/collections/software-dock, https://otsmanetwork.com/pages/create-your-company, https://otsmanetwork.com/pages/shopify-theme, https://otsmanetwork.com/collections/%D8%A8%D8%B1%D8%A7%D9%85%D8%AC-%D9%84%D8%A7%D8%A8%D8%AF-%D9%85%D9%86%D9%87%D8%A7 and https://otsmanetwork.com/customer_authentication/redirect and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://otsmanetwork.com/collections/frontpage/products/shopify-seo-dropshipping-store, https://otsmanetwork.com/collections/frontpage/products/shopify-store-creation-rpofessional-dropshipping-store and https://otsmanetwork.com/collections/frontpage/products/shopify-store-review use the same meta description. A description written for each page earns more clicks.

Your homepage links to 8 pages by a URL that isn't their canonical one, for example https://otsmanetwork.com/collections/%D8%B4%D9%88%D8%A8%D9%8A%D9%81%D8%A7%D9%8A, whose canonical is https://otsmanetwork.com/collections/%d8%b4%d9%88%d8%a8%d9%8a%d9%81%d8%a7%d9%8a. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://otsmanetwork.com/pages/create-your-company, https://otsmanetwork.com/pages/shopify-theme and https://otsmanetwork.com/customer_authentication/redirect have no <h1> headline, so visitors and search engines get no clear main topic.

https://otsmanetwork.com/pages/shopify-theme and https://otsmanetwork.com/pages/create-shopify-store have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

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

2 errors were logged to the browser console while the page loaded, for example “Identifier 'urlToPreload' has already been declared”.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: “over 150+ clients”. Pairing it with named testimonials or customer logos makes it far more convincing.

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 shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 274 words of visible text.

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