Tools & Wizards About Us
i4berlin.com screenshot

Report Summary

  • 64

    Performance

    Renders faster than
    78% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

i4berlin.com

i4berlin.com - This website is for sale! - i4berlin Resources and Information.

Page Load Speed

28.3 sec in total

First Response

4.3 sec

Resources Loaded

17 sec

Page Rendered

7 sec

i4berlin.com screenshot

About Website

Visit i4berlin.com now to see the best up-to-date I 4 Berlin content and also check out these interesting facts you probably never knew about i4berlin.com

This website is for sale! i4berlin.com is your first and best source for all of the information you’re looking for. From general topics to more of what you would expect to find here, i4berlin.com has ...

Visit i4berlin.com

Key Findings

We analyzed I4berlin.com page load time and found that the first response time was 4.3 sec and then it took 24 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

i4berlin.com performance score

64

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.0 s

100/100

10%

LCP (Largest Contentful Paint)

Value1.0 s

100/100

25%

SI (Speed Index)

Value3.2 s

91/100

10%

TBT (Total Blocking Time)

Value1,840 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.197

62/100

15%

TTI (Time to Interactive)

Value4.6 s

82/100

10%

Network Requests Diagram

www.i4berlin.com

4278 ms

normalize.css

233 ms

grid.css

202 ms

jquery.lightbox-0.5.css

313 ms

jquery.menu.css

314 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 93% of them (53 requests) were addressed to the original I4berlin.com, 4% (2 requests) were made to I4words.com and 2% (1 request) were made to Maps.google.com. The less responsive or slowest element that took the longest time to load (4.3 sec) belongs to the original domain I4berlin.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 214.1 kB (69%)

Content Size

310.2 kB

After Optimization

96.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of I4berlin.com main page is 310.2 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. 50% of websites need less resources to load. HTML takes 122.8 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 104.2 kB

  • Original 122.8 kB
  • After minification 94.6 kB
  • After compression 18.6 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 28.2 kB, which is 23% 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 104.2 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 165 B

  • Original 35.1 kB
  • After minification 35.0 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. I 4 Berlin images are well optimized though.

JavaScript Optimization

-54%

Potential reduce by 27.7 kB

  • Original 51.4 kB
  • After minification 51.4 kB
  • After compression 23.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 27.7 kB or 54% of the original size.

CSS Optimization

-81%

Potential reduce by 82.1 kB

  • Original 100.8 kB
  • After minification 86.6 kB
  • After compression 18.7 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. I4berlin.com needs all CSS files to be minified and compressed as it can save up to 82.1 kB or 81% of the original size.

Requests Breakdown

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

Requests Now

53

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.i4berlin.com

www.i4berlin.com

4278 ms

normalize.css

normalize.css

233 ms

grid.css

grid.css

202 ms

jquery.lightbox-0.5.css

jquery.lightbox-0.5.css

313 ms

jquery.menu.css

jquery.menu.css

314 ms

borders.css

borders.css

312 ms

jquery-ui.css

jquery-ui.css

286 ms

slider1.css

slider1.css

352 ms

css_color.php

css_color.php

352 ms

grid2.css

grid2.css

352 ms

jquery-1.11.0.min.js

jquery-1.11.0.min.js

384 ms

jquery-migrate-1.2.1.min.js

jquery-migrate-1.2.1.min.js

349 ms

jquery-ui-1.10.4.min.js

jquery-ui-1.10.4.min.js

1486 ms

jquery.maskedinput-1.3.1.min.js

jquery.maskedinput-1.3.1.min.js

349 ms

searchform.v1.js

searchform.v1.js

348 ms

jquery.gradient.js

jquery.gradient.js

329 ms

jquery.autosuggest.js

jquery.autosuggest.js

1303 ms

jquery.dimensions.js

jquery.dimensions.js

1304 ms

i4tracker.js

i4tracker.js

1303 ms

formValidate.js

formValidate.js

1303 ms

jquery.lightbox-0.5.js

jquery.lightbox-0.5.js

1432 ms

content.js

content.js

1432 ms

header.js

header.js

1432 ms

detectFlash.js

detectFlash.js

1432 ms

jquery.lazyload.min.js

jquery.lazyload.min.js

1419 ms

slider1_grid2.css

slider1_grid2.css

2273 ms

promoSlider.js,slider1_grid2.js

promoSlider.js,slider1_grid2.js

2237 ms

jquery.media.js

jquery.media.js

2422 ms

piwik.js

piwik.js

867 ms

imgtracker.php

imgtracker.php

812 ms

process_barnew.gif

process_barnew.gif

627 ms

betterprice.gif

betterprice.gif

765 ms

waitpage-veriSignnew.gif

waitpage-veriSignnew.gif

736 ms

Versign-BBB1.gif

Versign-BBB1.gif

736 ms

staticmap

staticmap

325 ms

VeriSign3.png

VeriSign3.png

322 ms

2_i4berlin_3931541.jpeg

2_i4berlin_3931541.jpeg

322 ms

2_i4berlin_3935276.jpeg

2_i4berlin_3935276.jpeg

322 ms

2_i4berlin_3946696.jpeg

2_i4berlin_3946696.jpeg

322 ms

3_i4berlin_4061493.jpeg

3_i4berlin_4061493.jpeg

322 ms

spacer.gif

spacer.gif

298 ms

1_i4berlin_dreamstime_11937349.jpg

1_i4berlin_dreamstime_11937349.jpg

373 ms

spacer.gif

spacer.gif

372 ms

imgtracker.php

imgtracker.php

373 ms

CenturyGothicBold.ttf

CenturyGothicBold.ttf

532 ms

Futura-CondensedBold.otf

Futura-CondensedBold.otf

530 ms

piwik.php

piwik.php

482 ms

ar_left.gif

ar_left.gif

365 ms

ar_right.gif

ar_right.gif

503 ms

top_seperator_line1.gif

top_seperator_line1.gif

469 ms

redphone.gif

redphone.gif

468 ms

top_seperator_line2.gif

top_seperator_line2.gif

524 ms

Futura-CondensedExtraBold.otf

Futura-CondensedExtraBold.otf

497 ms

browserrez.php

browserrez.php

154 ms

calimg.gif

calimg.gif

796 ms

ui-bg_inset-hard_100_fcfdfd_1x100.png

ui-bg_inset-hard_100_fcfdfd_1x100.png

401 ms

nr-1044.min.js

nr-1044.min.js

1281 ms

Accessibility Review

i4berlin.com accessibility score

63

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

<frame> or <iframe> elements do not have a title

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

i4berlin.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

i4berlin.com SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

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 doesn't use 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 I4berlin.com 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 I4berlin.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

i4berlin.com

Open Graph data is detected on the main page of I 4 Berlin. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: