metalyapi.com website review

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

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

About 1.6 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 8.1 s faster on a phone.

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

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

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

142 KiB could be saved by minifying CSS.

117 KiB could be saved by minifying JavaScript.

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

Polyfills for old browsers add 27 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

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

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

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

7 long tasks block the main thread while loading, the longest for 111 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.

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

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

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

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

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

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 66.3 MB in 79 requests on a phone: media 53.3 MB (14), images 8.6 MB (23) and stylesheets 1.6 MB (10). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (323 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

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

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

1 image has no alt text, which hurts accessibility and image search.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

Your title is only 28 characters: “Home Page - Metal Yapı Group”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

The homepage links to 35 pages on metalyapi.com and 5 external pages.

There is no https://metalyapi.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.

Your homepage links to https://metalyapi.com/tr, which answers with an error. Visitors hit a dead end and search engines drop it.

Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://metalyapi.com/about-us/code-of-ethics, whose canonical is https://metalyapi.com/code-of-ethics. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://metalyapi.com/projects, https://metalyapi.com/companies, https://metalyapi.com/unique-solutions, https://metalyapi.com/about-us/code-of-ethics, https://metalyapi.com/about-us/our-history and https://metalyapi.com/about-us/main-activity and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://metalyapi.com/contact has 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 14 pages linked from your homepage and read each the way a search engine does.

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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