siliconii.com website review

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

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

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

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

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

2 third-party services load with your homepage (Google Tag Manager and Google Analytics), adding 179 KiB and 111 ms of main-thread time.

1 long task block the main thread while loading, the longest for 61 ms. During a long task the page ignores taps.

About 15 KiB of CSS is downloaded but never applied on this page.

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.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Real visitors wait 5.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors see the first content after 3.0 s (75th percentile). Good is under 1.8 s.

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

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

Your largest element takes 4.3 s to render on a phone. Google's threshold for “good” is 2.5 s.

100 images have no width and height attributes, so the layout jumps as each one loads.

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

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 81 ms to 85 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 8.7 MB in 97 requests on a phone: images 5.4 MB (64), fonts 2.9 MB (4) and scripts 342 KiB (13). Under 2 MB keeps phones on slow connections fast.

2 images weigh 1.6 MB together. On a phone connection a single image that size takes seconds.

17 images (4.8 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.

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

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

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

Some lists contain elements other than list items, which screen readers announce wrongly.

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

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

ARIA role should be appropriate for the element: 16 elements on the page fail this check, rated minor by axe-core.

Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

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

Your title is only 7 characters: “(주)실리콘투”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

Your meta description is only 44 characters: “화장품 유통 무역 업체, 해외 판매 및 해외 마케팅 지원, 브랜드 영업대행 안내”. 70 to 160 characters is enough to sell the click.

1 link has no real href, so search engines can't follow it.

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

The homepage links to 70 pages on siliconii.com and 13 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://www.siliconii.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://www.siliconii.com/en, https://www.siliconii.com/jp, https://www.siliconii.com/sub/sub01_01.php, https://www.siliconii.com/sub/sub01_02.php, https://www.siliconii.com/sub/sub01_03.php and https://www.siliconii.com/sub/sub01_05.php and 9 others 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.siliconii.com/en, https://www.siliconii.com/jp, https://www.siliconii.com/sub/sub01_01.php, https://www.siliconii.com/sub/sub01_02.php and https://www.siliconii.com/sub/sub01_03.php and 10 others all use the title “(주)실리콘투”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.siliconii.com/en, https://www.siliconii.com/jp, https://www.siliconii.com/sub/sub01_01.php, https://www.siliconii.com/sub/sub01_02.php, https://www.siliconii.com/sub/sub01_03.php and https://www.siliconii.com/sub/sub01_05.php and 9 others use the same meta description. A description written for each page earns more clicks.

https://www.siliconii.com/en, https://www.siliconii.com/jp, https://www.siliconii.com/sub/sub01_01.php, https://www.siliconii.com/sub/sub01_02.php, https://www.siliconii.com/sub/sub01_03.php and https://www.siliconii.com/sub/sub01_05.php and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.siliconii.com/sub/sub01_01.php, https://www.siliconii.com/sub/sub01_05.php, https://www.siliconii.com/sub/sub01_04.php, https://www.siliconii.com/sub/sub02_01.php, https://www.siliconii.com/sub/sub02_09.php and https://www.siliconii.com/sub/sub02_02.php and 3 others 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 42 found) 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”.

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.

Social proof on the homepage: 25 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage shows no opening hours. If customers visit or call, show when.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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