seoulrobotics.tech website review

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

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

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

5 third-party services load with your homepage (Unpkg, Cloudflare CDN and jQuery CDN and others), adding 2.4 MB and 1.1 s of main-thread time.

Your mobile performance score is 55 (desktop: 73). Pages that score under 90 lose visitors before the first paint.

Unpkg costs a phone 987 ms of main-thread work and 102 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 95 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.8 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

JSDelivr CDN costs a phone 8 ms of main-thread work and 2.3 MB 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.

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

3 KiB could be saved by minifying CSS.

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

Your largest element takes 14.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Autonomous Logistics, Now.”.

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

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

18 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 67.2 MB in 64 requests on a phone: media 58.5 MB (9), images 6.0 MB (28) and fonts 2.2 MB (4). Under 2 MB keeps phones on slow connections fast.

3 images weigh 5.0 MB together. On a phone connection a single image that size takes seconds.

2 images are downloaded at several times the size a phone draws them, for example 4_ATS.jpg at 2,034 px wide, shown at 350 px. Resized copies would save about 2.8 MB.

6 images (5.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.

3 images further down the page (4.3 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 19.06 g of CO₂e: 2286.7 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”.

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

Links must have discernible text: 5 elements on the page fail this check, rated serious by axe-core.

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.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

Headings skip levels (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 twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 39 pages on seoulrobotics.tech and 10 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://seoulrobotics.tech/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://seoulrobotics.tech/technology, https://seoulrobotics.tech/company, https://seoulrobotics.tech/ir, https://seoulrobotics.tech/newsroom and https://seoulrobotics.tech/careers and 4 others all use the title “Seoul Robotics : B2B Autonomous Driving Technology”. Search engines can't tell which page to show for a search, so each competes with the others.

https://seoulrobotics.tech/technology, https://seoulrobotics.tech/company, https://seoulrobotics.tech/ir, https://seoulrobotics.tech/newsroom, https://seoulrobotics.tech/careers and https://seoulrobotics.tech/avm and 3 others use the same meta description. A description written for each page earns more clicks.

https://seoulrobotics.tech/technology, https://seoulrobotics.tech/company, https://seoulrobotics.tech/avm, https://seoulrobotics.tech/ayt and https://seoulrobotics.tech/ats have no <h1> headline, so visitors and search engines get no clear main topic.

https://seoulrobotics.tech/ir and https://seoulrobotics.tech/ayt took over 3 s to send their HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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

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

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