webcontentor.com website review

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

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

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

18 images could be 15.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

8 third-party services load with your homepage (Facebook, Google Tag Manager and jQuery CDN and others), adding 642 KiB and 329 ms of main-thread time.

About 32 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.

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

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

Your largest element takes 11.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Custom Software That Connects Your Systems and Simplifies O…”.

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

Visually, the page fills in at 5.0 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.

21 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 18.4 MB in 75 requests on a phone: images 17.9 MB (58), scripts 487 KiB (6) and fonts 43 KiB (1). Under 2 MB keeps phones on slow connections fast.

12 images weigh 15.9 MB together. On a phone connection a single image that size takes seconds.

4 images are downloaded at several times the size a phone draws them, for example ogmen.png at 1,322 px wide, shown at 298 px. Resized copies would save about 3.3 MB.

12 images (15.9 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.

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

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

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

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

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

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

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

The homepage links to 26 pages on webcontentor.com and 4 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.

https://www.webcontentor.com/ai-ml-solution.html, https://www.webcontentor.com/ui-ux.html, https://www.webcontentor.com/mobile-app-development.html, https://www.webcontentor.com/fullstack-development.html, https://www.webcontentor.com/gamified-demand-generation-tools.html and https://www.webcontentor.com/cloud-sass-solutions.html and 1 other have no <title>, so Google invents the link text in results.

https://www.webcontentor.com/ai-ml-solution.html, https://www.webcontentor.com/ui-ux.html, https://www.webcontentor.com/mobile-app-development.html, https://www.webcontentor.com/fullstack-development.html, https://www.webcontentor.com/gamified-demand-generation-tools.html and https://www.webcontentor.com/cloud-sass-solutions.html and 1 other declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

https://www.webcontentor.com/ai-ml-solution.html, https://www.webcontentor.com/ui-ux.html, https://www.webcontentor.com/mobile-app-development.html, https://www.webcontentor.com/fullstack-development.html, https://www.webcontentor.com/gamified-demand-generation-tools.html and https://www.webcontentor.com/cloud-sass-solutions.html and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

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

1 image failed to load on a phone, for example https://www.svgrepo.com/show/376356/aws.svg.

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://pro.fontawesome.com/releases/v5.15.4/css/all.css' from origin 'https://www.webcont…”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

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 form on the homepage, so every lead has to click through to another page first.

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

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

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