Tools & Wizards About Us
sourberry.org screenshot

Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

sourberry.org

sourberry - yakışıklı değil ama şirin

Page Load Speed

6.3 sec in total

First Response

298 ms

Resources Loaded

5.9 sec

Page Rendered

99 ms

sourberry.org screenshot

About Website

Welcome to sourberry.org homepage info - get ready to check Sourberry best content for Turkey right away, or after learning these important things about sourberry.org

sourberry radyo

Visit sourberry.org

Key Findings

We analyzed Sourberry.org page load time and found that the first response time was 298 ms and then it took 6 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

sourberry.org performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

26/100

10%

LCP (Largest Contentful Paint)

Value6.5 s

9/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value290 ms

80/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value9.9 s

27/100

10%

Network Requests Diagram

sourberry.org

298 ms

www.sourberry.org

371 ms

www.sourberry.org

751 ms

final.v7.css

493 ms

jq.pack.v3.js

602 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 5% of them (3 requests) were addressed to the original Sourberry.org, 19% (11 requests) were made to S3.s.sourberry.org and 17% (10 requests) were made to S.sourberry.org. The less responsive or slowest element that took the longest time to load (3.9 sec) relates to the external source S1.s.sourberry.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 45.9 kB (19%)

Content Size

244.3 kB

After Optimization

198.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Sourberry.org main page is 244.3 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. 25% of websites need less resources to load. Images take 111.1 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 42.8 kB

  • Original 55.1 kB
  • After minification 55.0 kB
  • After compression 12.3 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 42.8 kB or 78% of the original size.

Image Optimization

-2%

Potential reduce by 2.4 kB

  • Original 111.1 kB
  • After minification 108.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. Sourberry images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 631 B

  • Original 72.3 kB
  • After minification 72.3 kB
  • After compression 71.6 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.

CSS Optimization

-1%

Potential reduce by 51 B

  • Original 5.8 kB
  • After minification 5.8 kB
  • After compression 5.8 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. Sourberry.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 23 (42%)

Requests Now

55

After Optimization

32

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

sourberry.org

sourberry.org

298 ms

www.sourberry.org

www.sourberry.org

371 ms

www.sourberry.org

www.sourberry.org

751 ms

final.v7.css

final.v7.css

493 ms

jq.pack.v3.js

jq.pack.v3.js

602 ms

cufon.pack.v2.js

cufon.pack.v2.js

607 ms

player.v1.js

player.v1.js

509 ms

ga.js

ga.js

50 ms

s484.jpg

s484.jpg

607 ms

s7607.jpg

s7607.jpg

2189 ms

s7382.jpg

s7382.jpg

2772 ms

limon.gif

limon.gif

550 ms

s2330.jpg

s2330.jpg

2772 ms

exhibition.gif

exhibition.gif

959 ms

eksiduyuru.gif

eksiduyuru.gif

991 ms

logo.v1.png

logo.v1.png

99 ms

lnew.png

lnew.png

96 ms

pfacebook.v1.png

pfacebook.v1.png

99 ms

sg2.v1.gif

sg2.v1.gif

190 ms

logo-footer.v1.png

logo-footer.v1.png

193 ms

all.js

all.js

48 ms

s-genh.v2.png

s-genh.v2.png

191 ms

us8033.jpg

us8033.jpg

3785 ms

us8010.jpg

us8010.jpg

2842 ms

us8006.jpg

us8006.jpg

2843 ms

us7994.jpg

us7994.jpg

2934 ms

us7822.jpg

us7822.jpg

2934 ms

us7890.jpg

us7890.jpg

3026 ms

us7886.jpg

us7886.jpg

3027 ms

us8024.jpg

us8024.jpg

677 ms

us8004.jpg

us8004.jpg

694 ms

us8000.jpg

us8000.jpg

769 ms

us1252.jpg

us1252.jpg

786 ms

us7648.jpg

us7648.jpg

864 ms

us5352.jpg

us5352.jpg

879 ms

us7472.jpg

us7472.jpg

912 ms

gunlukakis-bg.v1.png

gunlukakis-bg.v1.png

268 ms

us8029.jpg

us8029.jpg

3795 ms

us8017.jpg

us8017.jpg

3794 ms

us8001.jpg

us8001.jpg

3797 ms

us7997.jpg

us7997.jpg

3798 ms

us5013.jpg

us5013.jpg

3799 ms

us1089.jpg

us1089.jpg

3869 ms

us777.jpg

us777.jpg

3886 ms

us6129.jpg

us6129.jpg

3887 ms

us8031.jpg

us8031.jpg

2257 ms

us8019.jpg

us8019.jpg

2350 ms

us8027.jpg

us8027.jpg

2443 ms

us8007.jpg

us8007.jpg

2471 ms

us7999.jpg

us7999.jpg

2479 ms

us7835.jpg

us7835.jpg

2549 ms

us7635.jpg

us7635.jpg

2555 ms

us871.jpg

us871.jpg

2563 ms

us7727.jpg

us7727.jpg

2572 ms

us7339.jpg

us7339.jpg

2641 ms

__utm.gif

__utm.gif

24 ms

all.js

all.js

6 ms

28 ms

Accessibility Review

sourberry.org accessibility score

71

Accessibility Issues

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.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

sourberry.org best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

sourberry.org SEO score

69

Search Engine Optimization Advices

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

Language and Encoding

  • Language Detected

    TR

  • Language Claimed

    TR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sourberry.org can be misinterpreted by Google and other search engines. Our service has detected that Turkish is used on the page, and it matches the claimed language. Our system also found out that Sourberry.org 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.

Social Sharing Optimization

sourberry.org

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