medyssey.com website review

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

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

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

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

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

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

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

1 third-party service load with your homepage (Google Fonts), adding 63 KiB and 0 ms of main-thread time.

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.

4 KiB could be saved by minifying JavaScript.

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

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

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

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

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

4 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 27.1 MB in 89 requests on a phone: images 26.5 MB (54), scripts 383 KiB (16) and stylesheets 64 KiB (16). Under 2 MB keeps phones on slow connections fast.

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

3 images are downloaded at several times the size a phone draws them, for example 0d07573e1cd5b39083bf471434e516b0.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 507 KiB.

9 images (16.1 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.

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

2 buttons have no accessible name, so screen readers announce just “button”.

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 8 characters: “Medyssey”. 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.

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

Open Graph is missing og:description, so shared links fall back to guesses.

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

The homepage links to 60 pages on medyssey.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://medyssey.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://medyssey.com/sub/load-slick.php and https://medyssey.com/sub/pop_privacy.php have no <title>, so Google invents the link text in results.

https://medyssey.com/product, https://medyssey.com/company/facts, https://medyssey.com/company/ibt, https://medyssey.com/company/officeskorea, https://medyssey.com/company/officesglobal and https://medyssey.com/media/news and 7 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://medyssey.com/main, https://medyssey.com/product, https://medyssey.com/company/facts, https://medyssey.com/company/ibt, https://medyssey.com/company/officeskorea and https://medyssey.com/company/officesglobal and 8 others all use the title “Medyssey”. Search engines can't tell which page to show for a search, so each competes with the others.

https://medyssey.com/product, https://medyssey.com/company/facts, https://medyssey.com/company/ibt, https://medyssey.com/company/officeskorea, https://medyssey.com/company/officesglobal and https://medyssey.com/media/news and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://medyssey.com/sub/load-slick.php and https://medyssey.com/sub/pop_privacy.php have no <h1> headline, so visitors and search engines get no clear main topic.

https://medyssey.com/product took over 3 s to send its HTML from our server.

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

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: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

Your longest form asks for 8 fields (6 required). Every extra field lowers completion.

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 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 1,169 words of visible text.

Opening the homepage sets 2 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.