Tools & Wizards About Us
pdr.org.tr screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    58% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

pdr.org.tr

Türk Psikolojik Danışma ve Rehberlik Derneği - Türk PDR-Der

Page Load Speed

10.1 sec in total

First Response

3.3 sec

Resources Loaded

6.3 sec

Page Rendered

367 ms

pdr.org.tr screenshot

About Website

Click here to check amazing PDR content for Turkey. Otherwise, check out these important facts you probably never knew about pdr.org.tr

Visit pdr.org.tr

Key Findings

We analyzed Pdr.org.tr page load time and found that the first response time was 3.3 sec and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

pdr.org.tr performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

4/100

25%

SI (Speed Index)

Value14.1 s

1/100

10%

TBT (Total Blocking Time)

Value520 ms

56/100

30%

CLS (Cumulative Layout Shift)

Value0.01

100/100

15%

TTI (Time to Interactive)

Value10.5 s

24/100

10%

Network Requests Diagram

pdr.org.tr

3346 ms

css

24 ms

css

36 ms

new-css.css

930 ms

Style1.css

666 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 92% of them (67 requests) were addressed to the original Pdr.org.tr, 5% (4 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Pdr.org.tr.

Page Optimization Overview & Recommendations

Page size can be reduced by 405.3 kB (14%)

Content Size

2.9 MB

After Optimization

2.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pdr.org.tr main page is 2.9 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. 60% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 61.2 kB

  • Original 72.6 kB
  • After minification 67.0 kB
  • After compression 11.4 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 61.2 kB or 84% of the original size.

Image Optimization

-1%

Potential reduce by 24.7 kB

  • Original 2.5 MB
  • After minification 2.4 MB

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. PDR images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 181.6 kB

  • Original 258.4 kB
  • After minification 231.6 kB
  • After compression 76.8 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 181.6 kB or 70% of the original size.

CSS Optimization

-85%

Potential reduce by 137.9 kB

  • Original 163.1 kB
  • After minification 144.4 kB
  • After compression 25.3 kB

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. Pdr.org.tr needs all CSS files to be minified and compressed as it can save up to 137.9 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (28%)

Requests Now

64

After Optimization

46

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pdr.org.tr

pdr.org.tr

3346 ms

css

css

24 ms

css

css

36 ms

new-css.css

new-css.css

930 ms

Style1.css

Style1.css

666 ms

jquery-1.4.3.min.js

jquery-1.4.3.min.js

883 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

1050 ms

menu.css

menu.css

541 ms

menu.js

menu.js

884 ms

INC_JS.js

INC_JS.js

691 ms

mm_menu.js

mm_menu.js

610 ms

scrolltopcontrol.js

scrolltopcontrol.js

617 ms

prettify.css

prettify.css

829 ms

font-awesome.css

font-awesome.css

831 ms

default.css

default.css

692 ms

light.css

light.css

695 ms

dark.css

dark.css

695 ms

bar.css

bar.css

787 ms

nivo-slider.css

nivo-slider.css

784 ms

style.css

style.css

802 ms

jquery-1.9.0.min.js

jquery-1.9.0.min.js

788 ms

jquery.nivo.slider.js

jquery.nivo.slider.js

794 ms

Menu_B.jpg

Menu_B.jpg

189 ms

bg2.jpg

bg2.jpg

797 ms

header-bar.png

header-bar.png

279 ms

container-bg1.png

container-bg1.png

268 ms

banner.png

banner.png

275 ms

slide40.jpg

slide40.jpg

586 ms

slide9.jpg

slide9.jpg

531 ms

slide45.jpg

slide45.jpg

745 ms

slide46.jpg

slide46.jpg

716 ms

slide47.jpg

slide47.jpg

563 ms

slide48.jpg

slide48.jpg

816 ms

slide49.jpg

slide49.jpg

887 ms

slide50.jpg

slide50.jpg

897 ms

slide51.jpg

slide51.jpg

1007 ms

slide52.jpg

slide52.jpg

1027 ms

slide53.jpg

slide53.jpg

951 ms

slide54.jpg

slide54.jpg

998 ms

slide55.jpg

slide55.jpg

1053 ms

slide56.jpg

slide56.jpg

1203 ms

slide57.jpg

slide57.jpg

1089 ms

slide10.jpg

slide10.jpg

1139 ms

odeme.png

odeme.png

1172 ms

icon_arama.gif

icon_arama.gif

1182 ms

Kutu_Alt.jpg

Kutu_Alt.jpg

1197 ms

empati2015.png

empati2015.png

1321 ms

photos.png

photos.png

1306 ms

Kerim_Saglam.jpg

Kerim_Saglam.jpg

1320 ms

logo-pdr-s.jpg

logo-pdr-s.jpg

1311 ms

pdr-dergi.jpg

pdr-dergi.jpg

1383 ms

bulten-k.jpg

bulten-k.jpg

1360 ms

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

23 ms

u-WUoqrET9fUeobQW7jkRT8E0i7KZn-EPnyo3HZu7kw.woff

u-WUoqrET9fUeobQW7jkRT8E0i7KZn-EPnyo3HZu7kw.woff

31 ms

DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff

DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff

43 ms

k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff

k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff

44 ms

logo-icerik.png

logo-icerik.png

1488 ms

uye_girisi.png

uye_girisi.png

1392 ms

dis-video.png

dis-video.png

1394 ms

pder-dergi.png

pder-dergi.png

1397 ms

pdr-afis-kongre-k.jpg

pdr-afis-kongre-k.jpg

1415 ms

loading.gif

loading.gif

1392 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1482 ms

Menu_A.jpg

Menu_A.jpg

1399 ms

Bas_BG.jpg

Bas_BG.jpg

1393 ms

but_bg_header.png

but_bg_header.png

1401 ms

Cizgi.png

Cizgi.png

1570 ms

footer-bg.png

footer-bg.png

1134 ms

count.asp

count.asp

1523 ms

scrolltop.png

scrolltop.png

1092 ms

Degistirmeyin.gif

Degistirmeyin.gif

164 ms

icon_haberkucuk.gif

icon_haberkucuk.gif

143 ms

bullets.png

bullets.png

137 ms

Accessibility Review

pdr.org.tr accessibility score

69

Accessibility Issues

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

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

pdr.org.tr best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

pdr.org.tr SEO score

77

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

Mobile Friendly

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/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    TR

  • Language Claimed

    EN

  • Encoding

    ISO-8859-9

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pdr.org.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 Pdr.org.tr main page’s claimed encoding is iso-8859-9. 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

pdr.org.tr

Open Graph description is not detected on the main page of PDR. 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: