orttool.com website review

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

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

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

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

7 third-party services load with your homepage (YouTube, Google Maps and GoDaddy and others), adding 1.7 MB and 1.1 s of main-thread time.

YouTube costs a phone 669 ms of main-thread work and 958 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.

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

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

Google Maps costs a phone 314 ms of main-thread work and 475 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.

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

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

Google Fonts costs a phone 0 ms of main-thread work and 294 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.

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.

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

Your largest element takes 89.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Manufacturing Solutions for Industry ORT is a supplier of c…”.

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

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

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

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 22.4 MB in 78 requests on a phone: images 20.6 MB (21), scripts 1.4 MB (27) and fonts 288 KiB (7). Under 2 MB keeps phones on slow connections fast.

NEWPictBuilding-cropped-1-768x421.png weighs 496 KiB. On a phone connection a single image that size takes seconds.

3 images (696 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.

2 images further down the page (550 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image is downloaded at several times the size a phone draws it, for example Ort-Vector-LOGO-NEW.png at 2,340 px wide, shown at 246 px. Resized copies would save about 131 KiB.

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

2 frames have no title, so screen-reader users cannot tell what they contain.

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

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

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

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

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 24 pages on orttool.com and 5 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://orttool.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://orttool.com/front_page/index.html, https://orttool.com/equipment-list/index.html and https://orttool.com/press-releases/index.html all use the title “Redirecting...”. Search engines can't tell which page to show for a search, so each competes with the others.

https://orttool.com/front_page/index.html, https://orttool.com/about/index.html, https://orttool.com/contact/index.html, https://orttool.com/equipment-list/index.html, https://orttool.com/certifications/index.html and https://orttool.com/press-releases/index.html and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://orttool.com/press-releases-2, whose canonical is https://orttool.com/press-releases-2/index.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://orttool.com/front_page/index.html, https://orttool.com/equipment-list/index.html and https://orttool.com/press-releases/index.html have no <h1> headline, so visitors and search engines get no clear main topic.

https://orttool.com/front_page/index.html, https://orttool.com/contact/index.html, https://orttool.com/equipment-list/index.html and https://orttool.com/press-releases/index.html 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 8 pages linked from your homepage and read each the way a search engine does.

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 “SCC Library has already been loaded on page”.

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

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.

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