3.2 sec in total
413 ms
2.3 sec
487 ms
Visit origin.berlin now to see the best up-to-date Origin content and also check out these interesting facts you probably never knew about origin.berlin
We build websites, web applications, media installations and help you measure your success along the way.
Visit origin.berlinWe analyzed Origin.berlin page load time and found that the first response time was 413 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
origin.berlin performance score
name
value
score
weighting
Value3.3 s
40/100
10%
Value4.1 s
47/100
25%
Value3.6 s
86/100
10%
Value0 ms
100/100
30%
Value0.05
99/100
15%
Value3.7 s
90/100
10%
413 ms
443 ms
46 ms
59 ms
113 ms
Our browser made a total of 21 requests to load all elements on the main page. We found that 86% of them (18 requests) were addressed to the original Origin.berlin, 5% (1 request) were made to Fonts.googleapis.com and 5% (1 request) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (756 ms) belongs to the original domain Origin.berlin.
Page size can be reduced by 13.6 kB (1%)
2.4 MB
2.4 MB
In fact, the total size of Origin.berlin main page is 2.4 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. 20% of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.
Potential reduce by 11.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 11.9 kB or 71% of the original size.
Potential reduce by 1.7 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. Origin images are well optimized though.
Potential reduce by 24 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 12 B
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. Origin.berlin has all CSS files already compressed.
We found no issues to fix!
15
15
The browser has sent 15 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Origin. According to our analytics all requests are already optimized.
origin.berlin
413 ms
origin.berlin
443 ms
icon
46 ms
bulma.min.css
59 ms
app.657a3df3.css
113 ms
chunk-vendors.e92f7635.js
447 ms
app.e237cf56.js
429 ms
gtm.js
127 ms
projects.json
112 ms
services.json
122 ms
jobs.json
120 ms
Nexa-Book.otf
320 ms
Nexa-Light.otf
320 ms
teaser-ubitricity.png
756 ms
telekom-teaser.jpg
511 ms
abb-teaser.jpg
406 ms
ubitricity-desktop.png
720 ms
complicated-desktop.png
505 ms
media-installation-teaser.jpg
633 ms
glow2.png
608 ms
Nexa-Bold-Italic.otf
703 ms
origin.berlin accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Links do not have a discernible name
origin.berlin best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
origin.berlin SEO score
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Origin.berlin 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 Origin.berlin 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.
origin.berlin
Open Graph data is detected on the main page of Origin. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: