Access osmangazi.bel.tr. Osmangazi Belediyesi

name

value

score

weighting

FCP (First Contentful Paint)

Value6.1 s

3/100

10%

LCP (Largest Contentful Paint)

Value18.0 s

0/100

25%

SI (Speed Index)

Value10.2 s

9/100

10%

TBT (Total Blocking Time)

Value630 ms

47/100

30%

CLS (Cumulative Layout Shift)

Value0.98

2/100

15%

TTI (Time to Interactive)

Value20.4 s

2/100

10%

osmangazi.bel.tr

1566 ms

osmangazi.bel.tr

2811 ms

conversion.js

89 ms

css

33 ms

css

50 ms

Our browser made a total of 152 requests to load all elements on the main page. We found that 86% of them (131 requests) were addressed to the original Osmangazi.bel.tr, 5% (8 requests) were made to Fonts.gstatic.com and 2% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Osmangazi.bel.tr.

Content Size

235.7 kB

After Optimization

58.3 kB

In fact, the total size of Osmangazi.bel.tr main page is 235.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. HTML takes 190.1 kB which makes up the majority of the site volume.

HTML Optimization

-93%

Potential reduce by 177.1 kB

Original 190.1 kB
After minification 85.7 kB
After compression 13.0 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 104.5 kB, which is 55% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 177.1 kB or 93% of the original size.

JavaScript Optimization

-0%

Potential reduce by 208 B

Original 45.5 kB
After minification 45.5 kB
After compression 45.3 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

Requests Now

140

After Optimization

The browser has sent 140 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Osmangazi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

TR
Language Claimed

N/A
Encoding

X-MAC-TURKISH

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Osmangazi.bel.tr can be misinterpreted by Google and other search engines. Our service has detected that Turkish is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Osmangazi.bel.tr main page’s claimed encoding is x-mac-turkish. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

Open Graph description is not detected on the main page of Osmangazi. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: