4.4 sec in total
609 ms
3.3 sec
448 ms
Welcome to freundcontainer.com homepage info - get ready to check Freundcontainer best content for United States right away, or after learning these important things about freundcontainer.com
Berlin Packaging is a hybrid packaging company supplying wholesale bottles, containers, innovative design, financing, and supply chain services across all markets.
Visit freundcontainer.comWe analyzed Freundcontainer.com page load time and found that the first response time was 609 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
freundcontainer.com performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value13.8 s
0/100
25%
Value21.1 s
0/100
10%
Value2,700 ms
3/100
30%
Value0.061
97/100
15%
Value23.8 s
1/100
10%
609 ms
544 ms
118 ms
187 ms
114 ms
Our browser made a total of 116 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Freundcontainer.com, 41% (47 requests) were made to Cdn11.bigcommerce.com and 9% (10 requests) were made to Cdn.segment.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Webeo-web-content.s3-eu-west-1.amazonaws.com.
Page size can be reduced by 300.1 kB (29%)
1.0 MB
729.7 kB
In fact, the total size of Freundcontainer.com main page is 1.0 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 466.5 kB which makes up the majority of the site volume.
Potential reduce by 238.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 238.9 kB or 78% of the original size.
Potential reduce by 366 B
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. Freundcontainer images are well optimized though.
Potential reduce by 60.7 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 60.7 kB or 13% of the original size.
Potential reduce by 85 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. Freundcontainer.com has all CSS files already compressed.
Number of requests can be reduced by 78 (69%)
113
35
The browser has sent 113 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Freundcontainer. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 63 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
freundcontainer.com
609 ms
www.berlinpackaging.com
544 ms
theme-bundle.polyfills.js
118 ms
theme-bundle.head_async.js
187 ms
tp.widget.bootstrap.min.js
114 ms
theme.css
191 ms
_berlin_header.css
184 ms
_berlin_body.css
185 ms
_fonts.css
186 ms
sweetalert2.css
186 ms
_hawksearch.css
204 ms
_web_rotate_360.css
207 ms
js
202 ms
neo29sbo9q.js
108 ms
compliance.webeo.js
111 ms
266283.js
180 ms
uc.js
182 ms
jquery-3.6.0.min.js
111 ms
_berlin_navPages-ea655c10-e07d-013c-e0df-0217943b7735.css
242 ms
663407dd13c84ae22da3700d_663407e213c84ae22da3719c.css
104 ms
slick.min.js
241 ms
global-assets-907bc9c8029e478b18575447267677c12de9918e.js
107 ms
custom_elements_asset_663407dd13c84ae22da3700d_663407e213c84ae22da3719c.js
174 ms
theme-bundle.main.js
237 ms
datatags-b0cffa9d082a6a7d67818f35604c03cfa484e996.js
198 ms
csrf-protection-header-95f3d9ac8c049e3ed132c83a168cf1d6a8ed0237.js
253 ms
visitor_stencil.js
252 ms
collector.js
172 ms
gtm.js
170 ms
analytics.min.js
462 ms
loader.js
334 ms
core.webeo.js
1264 ms
wt.php
448 ms
i.js
328 ms
loading.svg
306 ms
461 ms
Logo-01.svg
181 ms
loading.svg
142 ms
search.svg
143 ms
cart.svg
139 ms
search-black.svg
141 ms
search-red.svg
140 ms
chat-light.svg
301 ms
chat-dark.svg
281 ms
phone-black.svg
306 ms
phone-red.svg
303 ms
account-black.svg
307 ms
account-red.svg
425 ms
cart-black.svg
426 ms
cart-red.svg
423 ms
690 ms
895 ms
894 ms
hotjar-1998128.js
624 ms
engage.js
805 ms
insight.min.js
669 ms
index.php
248 ms
js
102 ms
destination
462 ms
core.js
592 ms
iframe_api
862 ms
uwt.js
582 ms
events.js
569 ms
bat.js
425 ms
runtime_6459738026535cda4232dc813c61447d.js
847 ms
399 ms
nobot
322 ms
nobot
813 ms
webtraxs.php
371 ms
settings
249 ms
theme-bundle.chunk.60.js
301 ms
870.bundle.6e2976b75e60ab2b2bf8.js
232 ms
tsub-middleware.bundle.77315eced46c5ae4c052.js
512 ms
theme-bundle.chunk.36.js
486 ms
modules.1a30a0a67c3c23c13060.js
517 ms
450 ms
sa.css
375 ms
sa.jpeg
393 ms
main.2bdc3040.js
309 ms
adsct
625 ms
adsct
440 ms
ajs-destination.bundle.ed53a26b6edc80c65d73.js
35 ms
www-widgetapi.js
58 ms
theme-bundle.chunk.52.js
56 ms
main-v2_e15248ef4ac8cdb300e79b7fe94d0d13.js
90 ms
cjs_min_3a843477d8e318f67237a66d0a58c542.js
116 ms
schemaFilter.bundle.5c2661f67b4b71a6d9bd.js
55 ms
199 ms
188 ms
238 ms
icon-sprite.svg
73 ms
icon-sprite-1.svg
52 ms
icon-sprite-2.svg
49 ms
icon-sprite-3.svg
73 ms
theme-bundle.chunk.59.js
71 ms
511c8312ec30f7f75599.js
60 ms
saq_pxl
21 ms
155 ms
theme-bundle.chunk.27.js
129 ms
optimizely.dynamic.js.gz
80 ms
facebook-pixel.dynamic.js.gz
79 ms
p
395 ms
50 ms
commons.a61d7bea37d2de5d4b69.js.gz
6 ms
fbevents.js
47 ms
theme-bundle.chunk.1.js
23 ms
theme-bundle.chunk.2.js
42 ms
theme-bundle.chunk.39.js
40 ms
theme-bundle.chunk.0.js
70 ms
theme-bundle.chunk.29.js
71 ms
209143491537815
55 ms
theme-bundle.chunk.6.js
28 ms
theme-bundle.chunk.24.js
69 ms
theme-bundle.chunk.4.js
23 ms
theme-bundle.chunk.21.js
16 ms
theme-bundle.chunk.25.js
15 ms
freundcontainer.com accessibility score
freundcontainer.com 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
Issues were logged in the Issues panel in Chrome Devtools
freundcontainer.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Document doesn't have a valid hreflang
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
EN
EN
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Freundcontainer.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 Freundcontainer.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
freundcontainer.com
Open Graph description is not detected on the main page of Freundcontainer. 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: