12.3 sec in total
709 ms
11.3 sec
248 ms
Click here to check amazing Yok content for Turkey. Otherwise, check out these important facts you probably never knew about yok.gov.tr
Yükseköğretim Kurulu Başkanlığı İnternet Sitesi
Visit yok.gov.trWe analyzed Yok.gov.tr page load time and found that the first response time was 709 ms and then it took 11.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
yok.gov.tr performance score
name
value
score
weighting
Value10.8 s
0/100
10%
Value24.6 s
0/100
25%
Value16.4 s
0/100
10%
Value3,790 ms
1/100
30%
Value0.161
72/100
15%
Value23.6 s
1/100
10%
709 ms
267 ms
271 ms
275 ms
712 ms
Our browser made a total of 156 requests to load all elements on the main page. We found that 97% of them (152 requests) were addressed to the original Yok.gov.tr, 1% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (6.9 sec) belongs to the original domain Yok.gov.tr.
Page size can be reduced by 2.0 MB (22%)
9.0 MB
7.0 MB
In fact, the total size of Yok.gov.tr main page is 9.0 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Images take 6.7 MB which makes up the majority of the site volume.
Potential reduce by 110.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 24.8 kB, which is 19% 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 110.0 kB or 84% of the original size.
Potential reduce by 221.7 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Yok images are well optimized though.
Potential reduce by 521.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 521.3 kB or 67% of the original size.
Potential reduce by 1.2 MB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Yok.gov.tr needs all CSS files to be minified and compressed as it can save up to 1.2 MB or 83% of the original size.
Number of requests can be reduced by 93 (61%)
153
60
The browser has sent 153 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yok. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and from 84 to 1 for CSS and as a result speed up the page load time.
yok.gov.tr
709 ms
main.css
267 ms
main.css
271 ms
main.css
275 ms
barebone.jsp
712 ms
main.css
279 ms
jquery-1.4.2.min.js
5 ms
main.js
159 ms
aui.css
809 ms
portal_1.css
137 ms
portal_2.css
149 ms
taglib_1.css
160 ms
taglib_2.css
162 ms
openid.css
273 ms
accessibility.css
281 ms
generic_portal.css
154 ms
add_content.css
169 ms
flyout.css
270 ms
panel_component.css
282 ms
panel_pagination.css
289 ms
position_helper.css
310 ms
auto_row.css
402 ms
undo_manager.css
417 ms
panel_page.css
425 ms
javascript_template.css
442 ms
portlet_item.css
450 ms
portlet_css_editor.css
535 ms
portlet_toolbar.css
551 ms
toolbar.css
561 ms
tree.css
579 ms
uploader.css
590 ms
page_settings.css
666 ms
notifications.css
684 ms
asset_category_selector.css
694 ms
asset_column.css
711 ms
tag_selector.css
727 ms
generic_portlet.css
791 ms
forms.css
794 ms
header_row.css
816 ms
preview.css
828 ms
rich_editor.css
845 ms
search_combobox.css
865 ms
separator.css
923 ms
top_links.css
924 ms
translation_manager.css
949 ms
asset_categories_summary.css
961 ms
asset_links.css
976 ms
calendar.css
890 ms
captcha.css
934 ms
categorization_filter.css
927 ms
diff.css
939 ms
diff_html.css
850 ms
discussion.css
858 ms
flags.css
881 ms
form_navigator.css
905 ms
header.css
903 ms
icon.css
838 ms
icon_help.css
840 ms
icon_list.css
849 ms
icon_menu.css
870 ms
input_localized.css
893 ms
input_move_boxes.css
811 ms
input_repeat.css
824 ms
language.css
834 ms
logo_selector.css
831 ms
preview.css
859 ms
ratings.css
809 ms
search_iterator.css
811 ms
search_toggle.css
824 ms
social_activities.css
831 ms
social_bookmarks.css
830 ms
tags_summary.css
863 ms
user_display.css
813 ms
webdav.css
818 ms
workflow_status.css
829 ms
base.css
140 ms
application.css
140 ms
layout.css
144 ms
dockbar.css
148 ms
navigation.css
143 ms
portlet.css
145 ms
forms.css
288 ms
extras.css
286 ms
custom.css
287 ms
custom_common.css
140 ms
green.css
137 ms
orange.css
143 ms
ga.js
45 ms
bodyback.png
138 ms
topback.png
137 ms
6c971a66-535d-44d5-a276-f6d4a982a0ac
343 ms
f0fac5c4-8883-4e4d-94b1-f7d11cc60c32
410 ms
ccf3e5b9-cc53-4509-ab83-7c0adeb4cffd
395 ms
bb61333f-9127-4897-af6f-ee1becdcdc24
399 ms
c98af099-ddc1-4898-b2e8-4097933b837a
405 ms
layout_set_logo
320 ms
doc-search-input_bg.png
454 ms
bg.png
480 ms
d6d348b4-c4c6-437a-97a2-81422e1104f5
714 ms
66baa159-dfac-4a2d-9982-43d4d18e001b
766 ms
b40fff65-ec8a-40e6-a0f7-7ee0d4eccecf
753 ms
693 ms
d7188065-805a-4107-8292-894a52d585ab
1411 ms
3fde7253-5486-482a-b8e1-ae17717ea3e2
761 ms
3713732e-9e53-4f91-92aa-f5066c210920
1023 ms
83c72ec1-9217-4038-ad1e-61faf4db703e
1005 ms
7dc7edd1-1431-4d59-a5dc-cdf65ad60654
1419 ms
asset_publisher.png
898 ms
history.png
902 ms
article
1228 ms
article
1612 ms
article
1194 ms
article
1202 ms
article
1658 ms
article
2110 ms
article
1523 ms
article
1698 ms
article
1850 ms
article
1709 ms
article
2108 ms
article
2072 ms
article
1917 ms
article
1978 ms
banner-nav_loading.gif
277 ms
article
2024 ms
__utm.gif
16 ms
1929 ms
pfdindisplaypro-thin-webfont.woff
2268 ms
article
2143 ms
article
2004 ms
article
2078 ms
article
2084 ms
d367a409-0faf-4134-82cf-d3518d92c18d
1958 ms
article
3574 ms
article
4259 ms
article
3648 ms
article
3049 ms
article
3680 ms
article
3720 ms
article
4745 ms
article
4147 ms
article
4754 ms
article
5316 ms
article
4599 ms
article
4561 ms
article
5797 ms
article
5347 ms
article
6910 ms
article
5139 ms
pause.png
4373 ms
prev.png
4431 ms
next.png
4483 ms
button_back.png
4577 ms
backlogo.png
4247 ms
slider_prev.png
4264 ms
slider_next.png
4384 ms
yok.gov.tr accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Names and labels
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.
Impact
Issue
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
yok.gov.tr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
yok.gov.tr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
TR
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yok.gov.tr can be misinterpreted by Google and other search engines. Our service has detected that Turkish is used on the page, and it does not match the claimed English language. Our system also found out that Yok.gov.tr main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
yok.gov.tr
Open Graph description is not detected on the main page of Yok. 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: