Tools & Wizards About Us
cansay.net screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

cansay.net

CAN-SAY®, CHINCHILLA ÜRETİM MERKEZİ, Çinçilla üretim merkezi

Page Load Speed

10 sec in total

First Response

3.6 sec

Resources Loaded

5.9 sec

Page Rendered

543 ms

cansay.net screenshot

About Website

Welcome to cansay.net homepage info - get ready to check CAN SAY best content for Turkey right away, or after learning these important things about cansay.net

Çinçilla nedir. Çinçilla nasıl üretilir, Çinçilla işinden nasıl para kazanılır, Çinçilla nereden alınır? Çincilla kime satılır? Çinçilla üretimi CANSAY

Visit cansay.net

Key Findings

We analyzed Cansay.net page load time and found that the first response time was 3.6 sec and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster. This domain responded with an error, which can significantly jeopardize Cansay.net rating and web reputation

Performance Metrics

cansay.net performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value9.4 s

0/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value290 ms

79/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value7.8 s

44/100

10%

Network Requests Diagram

www.cansay.net

3554 ms

style.css

290 ms

nggallery.css

287 ms

shutter-reloaded.css

288 ms

sociable.css

323 ms

Our browser made a total of 118 requests to load all elements on the main page. We found that 52% of them (61 requests) were addressed to the original Cansay.net, 17% (20 requests) were made to Um.simpli.fi and 3% (4 requests) were made to I.simpli.fi. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain Cansay.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 254.1 kB (22%)

Content Size

1.1 MB

After Optimization

888.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cansay.net main page is 1.1 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 804.6 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 57.1 kB

  • Original 82.0 kB
  • After minification 81.0 kB
  • After compression 24.9 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 57.1 kB or 70% of the original size.

Image Optimization

-6%

Potential reduce by 46.7 kB

  • Original 804.6 kB
  • After minification 757.9 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. CAN SAY images are well optimized though.

JavaScript Optimization

-56%

Potential reduce by 125.4 kB

  • Original 225.2 kB
  • After minification 221.1 kB
  • After compression 99.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 125.4 kB or 56% of the original size.

CSS Optimization

-80%

Potential reduce by 24.9 kB

  • Original 31.1 kB
  • After minification 22.8 kB
  • After compression 6.1 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. Cansay.net needs all CSS files to be minified and compressed as it can save up to 24.9 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 45 (48%)

Requests Now

93

After Optimization

48

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CAN SAY. 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 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.cansay.net

www.cansay.net

3554 ms

style.css

style.css

290 ms

nggallery.css

nggallery.css

287 ms

shutter-reloaded.css

shutter-reloaded.css

288 ms

sociable.css

sociable.css

323 ms

shutter-reloaded.js

shutter-reloaded.js

320 ms

jquery.js

jquery.js

719 ms

jquery-migrate.min.js

jquery-migrate.min.js

439 ms

jquery.cycle.all.min.js

jquery.cycle.all.min.js

438 ms

ngg.slideshow.min.js

ngg.slideshow.min.js

476 ms

jquery.easing.1.1.js

jquery.easing.1.1.js

479 ms

jcarousel.js

jcarousel.js

597 ms

cufon.js

cufon.js

597 ms

Hand_Of_Sean_400.font.js

Hand_Of_Sean_400.font.js

632 ms

effects.js

effects.js

635 ms

style.php

style.php

938 ms

logo.png

logo.png

164 ms

rss.png

rss.png

149 ms

delicious.png

delicious.png

162 ms

digg.png

digg.png

147 ms

body.jpg

body.jpg

655 ms

wrap.jpg

wrap.jpg

587 ms

menu.png

menu.png

328 ms

menu2.png

menu2.png

158 ms

top.png

top.png

156 ms

side.png

side.png

445 ms

109 ms

swfobject.js

swfobject.js

165 ms

facebook.png

facebook.png

147 ms

twitter.png

twitter.png

162 ms

linkedin.png

linkedin.png

148 ms

searchbg.png

searchbg.png

431 ms

sbutton.png

sbutton.png

294 ms

blueside.png

blueside.png

437 ms

redside.png

redside.png

478 ms

cansay4x25-80x60.jpg

cansay4x25-80x60.jpg

325 ms

chinchilla11-80x60.jpg

chinchilla11-80x60.jpg

394 ms

CAN-SAY2-80x60.jpg

CAN-SAY2-80x60.jpg

438 ms

Chinchilla-80x60.jpg

Chinchilla-80x60.jpg

486 ms

CAN-SAY-2-80x60.jpg

CAN-SAY-2-80x60.jpg

546 ms

greenside.png

greenside.png

573 ms

onyuzsmall.jpg

onyuzsmall.jpg

579 ms

onyuzsmall2.jpg

onyuzsmall2.jpg

588 ms

tab.js

tab.js

191 ms

bside.png

bside.png

771 ms

Chinchilla1-250x180.jpg

Chinchilla1-250x180.jpg

619 ms

cansay.jpg

cansay.jpg

672 ms

CAN-SAY-2-229x180.jpg

CAN-SAY-2-229x180.jpg

690 ms

Chinchilla-250x180.jpg

Chinchilla-250x180.jpg

697 ms

CAN-SAY2-250x180.jpg

CAN-SAY2-250x180.jpg

705 ms

chinchilla11.jpg

chinchilla11.jpg

778 ms

Chinchilla1-200x150.jpg

Chinchilla1-200x150.jpg

824 ms

CAN-SAY-2-200x150.jpg

CAN-SAY-2-200x150.jpg

799 ms

Chinchilla-200x150.jpg

Chinchilla-200x150.jpg

808 ms

CAN-SAY2-200x150.jpg

CAN-SAY2-200x150.jpg

817 ms

chinchilla11-200x112.jpg

chinchilla11-200x112.jpg

885 ms

cansay4x25-200x150.jpg

cansay4x25-200x150.jpg

904 ms

casing.png

casing.png

987 ms

slide.png

slide.png

968 ms

slidb.png

slidb.png

837 ms

more.png

more.png

842 ms

next.png

next.png

925 ms

footer.jpg

footer.jpg

1275 ms

ga.js

ga.js

22 ms

21 ms

__utm.gif

__utm.gif

12 ms

dpx.js

dpx.js

6 ms

tpid=1EE704455A01EF561B03413502B15127

tpid=1EE704455A01EF561B03413502B15127

7 ms

p

p

3 ms

dpx

dpx

3 ms

aol

aol

7 ms

mapuser

mapuser

4 ms

y_match

y_match

6 ms

match_redirect

match_redirect

4 ms

29931

29931

22 ms

match_redirect

match_redirect

3 ms

tpid=DA29559E5A01EF56AF480304029A1859

tpid=DA29559E5A01EF56AF480304029A1859

4 ms

lr

lr

4 ms

lr.gif

lr.gif

6 ms

match_redirect

match_redirect

4 ms

sync

sync

51 ms

match_redirect

match_redirect

5 ms

DA29559E5A01EF56AF480304029A1859

DA29559E5A01EF56AF480304029A1859

31 ms

60 ms

match_redirect

match_redirect

3 ms

ProfilesEngineServlet

ProfilesEngineServlet

8 ms

ProfilesEngineServlet

ProfilesEngineServlet

282 ms

tc.js

tc.js

7 ms

p

p

143 ms

v2

v2

44 ms

dpx

dpx

4 ms

xrefid.xgi

xrefid.xgi

6 ms

ca.png

ca.png

157 ms

tap.php

tap.php

7 ms

exelate

exelate

4 ms

19 ms

17 ms

26 ms

spotx_match

spotx_match

3 ms

52154.gif

52154.gif

7 ms

fb_match

fb_match

4 ms

u.php

u.php

76 ms

an

an

3 ms

lj_match

lj_match

3 ms

merge

merge

4 ms

cw_match

cw_match

4 ms

rtset

rtset

19 ms

rb_match

rb_match

3 ms

tap.php

tap.php

6 ms

ox_match

ox_match

3 ms

sd

sd

4 ms

pm_match

pm_match

5 ms

Pug

Pug

54 ms

pixel

pixel

21 ms

g_match

g_match

4 ms

match_redirect

match_redirect

4 ms

pixel

pixel

37 ms

aa_px

aa_px

4 ms

Accessibility Review

cansay.net accessibility score

78

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

cansay.net best practices score

67

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

cansay.net SEO score

92

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

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

    TR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cansay.net 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 Cansay.net 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

cansay.net

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