sedefshipyard.com website review

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

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

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

5 files are served with short cache lifetimes, so returning visitors download them again (192 KiB).

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and JSDelivr CDN and others), adding 966 KiB and 517 ms of main-thread time.

JSDelivr CDN costs a phone 123 ms of main-thread work and 311 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 43 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

Polyfills for old browsers add 12 KiB JavaScript that modern phones do not need.

Desktop scores 79 but mobile only 53. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

Your largest element takes 19.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Your browser does not…”.

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

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

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

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

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

12 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 4.4 MB in 65 requests on a phone: images 3.3 MB (30), scripts 835 KiB (15) and fonts 118 KiB (4). Under 2 MB keeps phones on slow connections fast.

hamburg_linkedin.jpg weighs 535 KiB. On a phone connection a single image that size takes seconds.

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

1 image is downloaded at several times the size a phone draws it, for example sedef-virtual-tour.jpg at 1,920 px wide, shown at 366 px. Resized copies would save about 249 KiB.

2 images further down the page (50 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 1.25 g of CO₂e: 150.2 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”.

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

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

25 images have no alt text, which hurts accessibility and image search.

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

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

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 canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

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

The homepage links to 81 pages on sedefshipyard.com and 14 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://sedefshipyard.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://sedefshipyard.com/en/video.html has no <title>, so Google invents the link text in results.

https://sedefshipyard.com/en, https://sedefshipyard.com/en/kurumsal.aspx, https://sedefshipyard.com/en/tersane.aspx, https://sedefshipyard.com/en/yerlesim-planlari.aspx, https://sedefshipyard.com/en/projects.aspx and https://sedefshipyard.com/en/arge.aspx and 3 others all use the title “Sedef Shipyard | Turkon Holding”. Search engines can't tell which page to show for a search, so each competes with the others.

https://sedefshipyard.com/tr, https://sedefshipyard.com/en/kurumsal.aspx, https://sedefshipyard.com/en/tersane.aspx, https://sedefshipyard.com/en/yerlesim-planlari.aspx, https://sedefshipyard.com/en/projects.aspx and https://sedefshipyard.com/en/arge.aspx and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://sedefshipyard.com/tr, https://sedefshipyard.com/en/yerlesim-planlari.aspx, https://sedefshipyard.com/en/projects.aspx, https://sedefshipyard.com/sanaltur, https://sedefshipyard.com/en/iletisim.aspx and https://sedefshipyard.com/en/video.html and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

https://sedefshipyard.com/sanaltur 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.

https://sedefshipyard.com/en/haberler.aspx, https://sedefshipyard.com/sanaltur, https://sedefshipyard.com/en/iletisim.aspx and https://sedefshipyard.com/en/video.html took over 3 s to send their HTML from our server.

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

18 of 24 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

6 errors were logged to the browser console while the page loaded, for example “Loading the stylesheet 'http://fonts.googleapis.com/css?family=PT+Sans:400,700' violates the following Content Security…”.

1 image is served at too low a resolution for sharp phone screens.

Chrome logged issues while loading the page (“Content security policy”).

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 109 words of visible text; thin pages give Google and first-time buyers little to go on.

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.

Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Meta Pixel (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 3 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 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.