Tools & Wizards About Us
witter.be screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

witter.be

WITTER - concept creation, graphic design & web development

Page Load Speed

2.3 sec in total

First Response

473 ms

Resources Loaded

1.7 sec

Page Rendered

73 ms

witter.be screenshot

About Website

Welcome to witter.be homepage info - get ready to check WITTER best content right away, or after learning these important things about witter.be

POFO is a highly creative, modern, visually stunning and Bootstrap responsive multipurpose agency and portfolio HTML5 template with 25 ready home page demos.

Visit witter.be

Key Findings

We analyzed Witter.be page load time and found that the first response time was 473 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

witter.be performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value9.7 s

0/100

25%

SI (Speed Index)

Value9.3 s

13/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.019

100/100

15%

TTI (Time to Interactive)

Value7.8 s

45/100

10%

Network Requests Diagram

witter.be

473 ms

w

281 ms

99 ms

animate.css

95 ms

bootstrap.min.css

287 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 74% of them (48 requests) were addressed to the original Witter.be, 23% (15 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 (738 ms) belongs to the original domain Witter.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 121.2 kB (33%)

Content Size

370.1 kB

After Optimization

248.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Witter.be main page is 370.1 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 191.7 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 7.6 kB

  • Original 9.0 kB
  • After minification 5.2 kB
  • After compression 1.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. This page needs HTML code to be minified as it can gain 3.8 kB, which is 42% 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 7.6 kB or 84% of the original size.

Image Optimization

-5%

Potential reduce by 197 B

  • Original 3.8 kB
  • After minification 3.6 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. WITTER images are well optimized though.

JavaScript Optimization

-29%

Potential reduce by 54.8 kB

  • Original 191.7 kB
  • After minification 191.7 kB
  • After compression 136.9 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 54.8 kB or 29% of the original size.

CSS Optimization

-35%

Potential reduce by 58.6 kB

  • Original 165.5 kB
  • After minification 165.5 kB
  • After compression 106.9 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. Witter.be needs all CSS files to be minified and compressed as it can save up to 58.6 kB or 35% of the original size.

Requests Breakdown

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

Requests Now

42

After Optimization

3

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

witter.be

witter.be

473 ms

w

w

281 ms

99 ms

animate.css

animate.css

95 ms

bootstrap.min.css

bootstrap.min.css

287 ms

et-line-icons.css

et-line-icons.css

183 ms

font-awesome.min.css

font-awesome.min.css

186 ms

themify-icons.css

themify-icons.css

184 ms

swiper.min.css

swiper.min.css

188 ms

justified-gallery.min.css

justified-gallery.min.css

184 ms

magnific-popup.css

magnific-popup.css

274 ms

settings.css

settings.css

273 ms

layers.css

layers.css

276 ms

navigation.css

navigation.css

277 ms

bootsnav.css

bootsnav.css

278 ms

style.css

style.css

496 ms

responsive.css

responsive.css

484 ms

jquery.js

jquery.js

465 ms

modernizr.js

modernizr.js

365 ms

bootstrap.min.js

bootstrap.min.js

373 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

375 ms

skrollr.min.js

skrollr.min.js

457 ms

smooth-scroll.js

smooth-scroll.js

463 ms

jquery.appear.js

jquery.appear.js

466 ms

bootsnav.js

bootsnav.js

584 ms

jquery.nav.js

jquery.nav.js

585 ms

wow.min.js

wow.min.js

585 ms

page-scroll.js

page-scroll.js

585 ms

swiper.min.js

swiper.min.js

590 ms

jquery.count-to.js

jquery.count-to.js

585 ms

jquery.stellar.js

jquery.stellar.js

645 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

651 ms

isotope.pkgd.min.js

isotope.pkgd.min.js

654 ms

imagesloaded.pkgd.min.js

imagesloaded.pkgd.min.js

654 ms

classie.js

classie.js

665 ms

hamburger-menu.js

hamburger-menu.js

675 ms

counter.js

counter.js

735 ms

jquery.fitvids.js

jquery.fitvids.js

736 ms

equalize.min.js

equalize.min.js

738 ms

skill.bars.jquery.js

skill.bars.jquery.js

651 ms

justified-gallery.min.js

justified-gallery.min.js

580 ms

jquery.easypiechart.min.js

jquery.easypiechart.min.js

587 ms

instafeed.min.js

instafeed.min.js

646 ms

retina.min.js

retina.min.js

644 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

644 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

560 ms

main.js

main.js

586 ms

logo.png

logo.png

602 ms

css

css

34 ms

css

css

51 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

20 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

23 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

28 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

35 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

35 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

36 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

35 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

35 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

34 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

44 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

46 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

43 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

46 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

46 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

46 ms

Accessibility Review

witter.be accessibility score

73

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.

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

witter.be 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

witter.be 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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

witter.be

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