Tools & Wizards About Us
tellows.ch screenshot

Report Summary

  • 74

    Performance

    Renders faster than
    83% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

tellows.ch

Wer ruft an? Telefonnummern Rückwärtssuche und Anruferkennung - tellows

Page Load Speed

2.6 sec in total

First Response

201 ms

Resources Loaded

2.1 sec

Page Rendered

310 ms

tellows.ch screenshot

About Website

Click here to check amazing Tellows content for Switzerland. Otherwise, check out these important facts you probably never knew about tellows.ch

Du suchst Details zu der Nummer, die dich angerufen hat? Dann bist du hier richtig in der großen Community zu Telefonnummern. Schau dir die Kommentare anderer User an und bewerte selbst.

Visit tellows.ch

Key Findings

We analyzed Tellows.ch page load time and found that the first response time was 201 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

tellows.ch performance score

74

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

85/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

68/100

25%

SI (Speed Index)

Value2.5 s

98/100

10%

TBT (Total Blocking Time)

Value480 ms

60/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.7 s

56/100

10%

Network Requests Diagram

tellows.ch

201 ms

www.tellows.ch

423 ms

201 ms

192 ms

adcode.js

5 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 24% of them (16 requests) were addressed to the original Tellows.ch, 13% (9 requests) were made to Apis.google.com and 10% (7 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (734 ms) relates to the external source Static.xx.fbcdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 373.0 kB (51%)

Content Size

731.9 kB

After Optimization

358.9 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Tellows.ch main page is 731.9 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. 55% of websites need less resources to load. Javascripts take 378.9 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 132.6 kB

  • Original 183.8 kB
  • After minification 175.8 kB
  • After compression 51.2 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 132.6 kB or 72% of the original size.

Image Optimization

-5%

Potential reduce by 7.7 kB

  • Original 169.2 kB
  • After minification 161.5 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. Tellows images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 232.7 kB

  • Original 378.9 kB
  • After minification 378.8 kB
  • After compression 146.2 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 232.7 kB or 61% of the original size.

Requests Breakdown

Number of requests can be reduced by 39 (60%)

Requests Now

65

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tellows.ch

tellows.ch

201 ms

www.tellows.ch

www.tellows.ch

423 ms

201 ms

192 ms

adcode.js

adcode.js

5 ms

plusone.js

plusone.js

104 ms

gpt.js

gpt.js

32 ms

ga.js

ga.js

46 ms

bkg_body_n.gif

bkg_body_n.gif

7 ms

spritemap.png

spritemap.png

39 ms

logo4.png

logo4.png

43 ms

tv-logo.gif

tv-logo.gif

13 ms

lookup_ico_b.png

lookup_ico_b.png

10 ms

search_btn_b.gif

search_btn_b.gif

9 ms

error.gif

error.gif

8 ms

con-bgv.png

con-bgv.png

10 ms

con-bgv-top.png

con-bgv-top.png

39 ms

tellowsvisual.jpg

tellowsvisual.jpg

394 ms

sprites_score.png

sprites_score.png

39 ms

pubads_impl_81.js

pubads_impl_81.js

32 ms

adp.php

adp.php

344 ms

__utm.gif

__utm.gif

50 ms

ads

ads

216 ms

container.html

container.html

18 ms

like.php

like.php

159 ms

like.php

like.php

141 ms

vpc6VNjRPXV.js

vpc6VNjRPXV.js

494 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

572 ms

ads

ads

344 ms

vpc6VNjRPXV.js

vpc6VNjRPXV.js

734 ms

deliver2

deliver2

179 ms

admaxxpop2.js

admaxxpop2.js

101 ms

expansion_embed.js

expansion_embed.js

53 ms

ads

ads

84 ms

js

js

164 ms

osd.js

osd.js

86 ms

438 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

79 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

107 ms

fastbutton

fastbutton

178 ms

fastbutton

fastbutton

175 ms

ad-loading.bmp

ad-loading.bmp

518 ms

414 ms

getads.js

getads.js

50 ms

ads

ads

267 ms

t.js

t.js

141 ms

postmessageRelay

postmessageRelay

127 ms

img

img

167 ms

pixel

pixel

144 ms

ck-confirm

ck-confirm

109 ms

rs=AGLTcCNqicBbTRy2Ny4TeyhsrBuZucE7Kg

rs=AGLTcCNqicBbTRy2Ny4TeyhsrBuZucE7Kg

47 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

42 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

40 ms

api.js

api.js

60 ms

core:rpc:shindig.random:shindig.sha1.js

core:rpc:shindig.random:shindig.sha1.js

164 ms

2536007149-postmessagerelay.js

2536007149-postmessagerelay.js

103 ms

Q116_Wu_Com_Awareness_V3_D_728x90_EN_US.jpg

Q116_Wu_Com_Awareness_V3_D_728x90_EN_US.jpg

164 ms

lidar.js

lidar.js

147 ms

sbhK2lTE.js

sbhK2lTE.js

120 ms

abg.js

abg.js

109 ms

m_js_controller.js

m_js_controller.js

143 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

107 ms

16724375845369557913

16724375845369557913

183 ms

cTrvNaRi.html

cTrvNaRi.html

52 ms

s

s

132 ms

x_button_blue2.png

x_button_blue2.png

64 ms

E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js

E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js

14 ms

Accessibility Review

tellows.ch accessibility score

81

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

tellows.ch 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

Missing source maps for large first-party JavaScript

SEO Factors

tellows.ch SEO score

79

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

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tellows.ch can be misinterpreted by Google and other search engines. Our service has detected that German 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 Tellows.ch 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

tellows.ch

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