Tools & Wizards About Us
traffective.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

traffective.com

Traffective – we add value | Traffective

Page Load Speed

3.3 sec in total

First Response

675 ms

Resources Loaded

2.2 sec

Page Rendered

463 ms

traffective.com screenshot

About Website

Welcome to traffective.com homepage info - get ready to check Traffective best content for Germany right away, or after learning these important things about traffective.com

Wir stehen Ihnen mit der Traffective Monetarisierungsplattform und Lösungen für alle Belange der Werbefinanzierung jederzeit zur Seite.

Visit traffective.com

Key Findings

We analyzed Traffective.com page load time and found that the first response time was 675 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

traffective.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value15.1 s

0/100

25%

SI (Speed Index)

Value11.8 s

4/100

10%

TBT (Total Blocking Time)

Value3,530 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value16.7 s

5/100

10%

Network Requests Diagram

traffective.com

675 ms

css

23 ms

foundation.css

613 ms

app.css

313 ms

responsiveslides.css

210 ms

Our browser made a total of 93 requests to load all elements on the main page. We found that 39% of them (36 requests) were addressed to the original Traffective.com, 26% (24 requests) were made to Google.com and 13% (12 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (778 ms) belongs to the original domain Traffective.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 619.0 kB (39%)

Content Size

1.6 MB

After Optimization

984.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-70%

Potential reduce by 14.3 kB

  • Original 20.4 kB
  • After minification 17.8 kB
  • After compression 6.1 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 2.6 kB, which is 13% 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 14.3 kB or 70% of the original size.

Image Optimization

-5%

Potential reduce by 33.8 kB

  • Original 719.8 kB
  • After minification 685.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. Traffective images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 516.5 kB

  • Original 797.5 kB
  • After minification 779.7 kB
  • After compression 281.0 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 516.5 kB or 65% of the original size.

CSS Optimization

-83%

Potential reduce by 54.4 kB

  • Original 65.5 kB
  • After minification 52.0 kB
  • After compression 11.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. Traffective.com needs all CSS files to be minified and compressed as it can save up to 54.4 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

86

After Optimization

50

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

traffective.com

traffective.com

675 ms

css

css

23 ms

foundation.css

foundation.css

613 ms

app.css

app.css

313 ms

responsiveslides.css

responsiveslides.css

210 ms

elastislide.css

elastislide.css

221 ms

lightbox.css

lightbox.css

320 ms

media.css

media.css

295 ms

jquery.min.js

jquery.min.js

30 ms

responsiveslides.min.js

responsiveslides.min.js

316 ms

modernizr.custom.17475.js

modernizr.custom.17475.js

375 ms

jquerypp.custom.js

jquerypp.custom.js

304 ms

jquery.elastislide.js

jquery.elastislide.js

537 ms

jquery.js

jquery.js

328 ms

jquery.sticky.js

jquery.sticky.js

437 ms

scrolling.js

scrolling.js

405 ms

lightbox.js

lightbox.js

638 ms

adsbygoogle.js

adsbygoogle.js

5 ms

pattern.png

pattern.png

105 ms

logo.png

logo.png

232 ms

en_on.png

en_on.png

108 ms

2.jpg

2.jpg

778 ms

1.jpg

1.jpg

435 ms

3.jpg

3.jpg

666 ms

bullet.png

bullet.png

207 ms

sascha.jpg

sascha.jpg

530 ms

heiko.jpg

heiko.jpg

508 ms

matthias.jpg

matthias.jpg

489 ms

adam.jpg

adam.jpg

530 ms

top.png

top.png

549 ms

pdf_icon.gif

pdf_icon.gif

643 ms

ca-pub-5395794454262600.js

ca-pub-5395794454262600.js

105 ms

embed

embed

174 ms

line_white.jpg

line_white.jpg

620 ms

line_1.jpg

line_1.jpg

620 ms

line_2.jpg

line_2.jpg

643 ms

Social_google.png

Social_google.png

670 ms

Social_fb.png

Social_fb.png

729 ms

Social_twitter.png

Social_twitter.png

729 ms

Social_blog.png

Social_blog.png

729 ms

Social_youtube.png

Social_youtube.png

748 ms

adsbygoogle.js

adsbygoogle.js

39 ms

4cKlrioa77J2iqTqBgkRWg.ttf

4cKlrioa77J2iqTqBgkRWg.ttf

51 ms

zrt_lookup.html

zrt_lookup.html

26 ms

show_ads_impl.js

show_ads_impl.js

80 ms

js

js

88 ms

init_embed.js

init_embed.js

87 ms

common.js

common.js

65 ms

map.js

map.js

79 ms

google4.png

google4.png

35 ms

overlay.js

overlay.js

34 ms

util.js

util.js

102 ms

onion.js

onion.js

99 ms

search_impl.js

search_impl.js

120 ms

stats.js

stats.js

76 ms

openhand_8_8.cur

openhand_8_8.cur

67 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

66 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

111 ms

kh

kh

106 ms

transparent.png

transparent.png

39 ms

controls.js

controls.js

55 ms

vt

vt

116 ms

vt

vt

230 ms

vt

vt

219 ms

vt

vt

147 ms

vt

vt

144 ms

vt

vt

145 ms

vt

vt

151 ms

vt

vt

192 ms

vt

vt

213 ms

vt

vt

197 ms

vt

vt

205 ms

vt

vt

241 ms

vt

vt

288 ms

vt

vt

289 ms

vt

vt

251 ms

vt

vt

259 ms

vt

vt

274 ms

vt

vt

278 ms

vt

vt

298 ms

vt

vt

314 ms

vt

vt

313 ms

vt

vt

354 ms

vt

vt

330 ms

css

css

110 ms

entity11.png

entity11.png

65 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

52 ms

mapcnt6.png

mapcnt6.png

44 ms

tmapctrl.png

tmapctrl.png

44 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

71 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

81 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

92 ms

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

107 ms

Accessibility Review

traffective.com accessibility score

86

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

Form elements do not have associated labels

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

traffective.com 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

SEO Factors

traffective.com SEO score

91

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

    DE

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

traffective.com

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