wizardinnovations.us website review

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

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

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

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

Your mobile performance score is 45. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

The page has 3,059 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

8 third-party services load with your homepage (Google Tag Manager, Google CDN and jQuery CDN and others), adding 1.6 MB and 783 ms of main-thread time.

Google Tag Manager costs a phone 623 ms of main-thread work and 928 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.

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

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

Google CDN costs a phone 107 ms of main-thread work and 352 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.

Cloudflare CDN costs a phone 10 ms of main-thread work and 304 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.

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

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

5 KiB could be saved by minifying JavaScript.

Your largest element takes 28.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “To help you cut through, we bring together technical brilli…”.

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

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

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

The layout shifts by 0.218 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Scripts block taps and scrolling for 327 ms in total while the page loads. Good is under 200 ms.

8 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.7 MB in 147 requests on a phone: images 12.9 MB (102), media 3.3 MB (2) and scripts 1.5 MB (20). Under 2 MB keeps phones on slow connections fast.

5 images weigh 3.0 MB together. On a phone connection a single image that size takes seconds.

12 images are downloaded at several times the size a phone draws them, for example hero-white.gif at 1,500 px wide, shown at 374 px. Resized copies would save about 2.3 MB.

38 images (8.4 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.

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

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 49 elements on the page fail this check, rated moderate by axe-core.

Headings should not be empty: 32 elements on the page fail this check, rated minor by axe-core.

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

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

Your title is 90 characters, so Google will cut it off around 60: “Custom Website | Mobile App | Tech Solutions | SAAS In Houston TX | Wizard Innovations LLC”.

There are 136 <h1> headlines (“Featured In”, “Featured In” and “Website Design & Development 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.

Structured data found (WebSite) but with 1 problem, for example “WebSite: potentialAction.target is not an absolute URL ("{search_term_string}")”.

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

No XML sitemap at https://wizardinnovations.us/sitemap.xml, so Google discovers your pages only by following links.

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 58 pages on wizardinnovations.us and 18 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://wizardinnovations.us/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://wizardinnovations.us/case-study, https://wizardinnovations.us/case-study/aris360 and https://wizardinnovations.us/case-study/docudash have no <title>, so Google invents the link text in results.

https://wizardinnovations.us/custom-software-development and https://wizardinnovations.us/contact all use the title “Contact Us - Wizard Innovations”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://wizardinnovations.us/about, https://wizardinnovations.us/custom-software-development, https://wizardinnovations.us/website-design-development, https://wizardinnovations.us/mobile-app-development, https://wizardinnovations.us/search-engine-optimization and https://wizardinnovations.us/game-development and 9 others use the same meta description. A description written for each page earns more clicks.

https://wizardinnovations.us/case-study, https://wizardinnovations.us/contact, https://wizardinnovations.us/case-study/aris360 and https://wizardinnovations.us/case-study/docudash have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

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.

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.

The homepage carries about 2,797 words of visible text.

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