Tools & Wizards About Us
berker.com screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

berker.com

Welcome to Berker.com

Page Load Speed

3.8 sec in total

First Response

816 ms

Resources Loaded

2.9 sec

Page Rendered

145 ms

berker.com screenshot

About Website

Click here to check amazing Berker content for Iran. Otherwise, check out these important facts you probably never knew about berker.com

Main navigation

Visit berker.com

Key Findings

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

Performance Metrics

berker.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

59/100

10%

LCP (Largest Contentful Paint)

Value11.7 s

0/100

25%

SI (Speed Index)

Value7.7 s

24/100

10%

TBT (Total Blocking Time)

Value1,230 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0.661

8/100

15%

TTI (Time to Interactive)

Value10.2 s

25/100

10%

Network Requests Diagram

www.berker.com

816 ms

app.min.css

560 ms

berker.min.css

286 ms

modernizr.custom.min.js

379 ms

es5-shim.min.js

426 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 75% of them (21 requests) were addressed to the original Berker.com, 14% (4 requests) were made to Googletagmanager.com and 7% (2 requests) were made to Unpkg.com. The less responsive or slowest element that took the longest time to load (972 ms) belongs to the original domain Berker.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 611.9 kB (36%)

Content Size

1.7 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Berker.com main page is 1.7 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. 65% of websites need less resources to load. Images take 610.1 kB which makes up the majority of the site volume.

HTML Optimization

-93%

Potential reduce by 99.0 kB

  • Original 106.1 kB
  • After minification 42.9 kB
  • After compression 7.0 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 63.1 kB, which is 60% 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 99.0 kB or 93% of the original size.

Image Optimization

-2%

Potential reduce by 14.1 kB

  • Original 610.1 kB
  • After minification 596.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. Berker images are well optimized though.

JavaScript Optimization

-19%

Potential reduce by 109.7 kB

  • Original 565.7 kB
  • After minification 565.4 kB
  • After compression 455.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 109.7 kB or 19% of the original size.

CSS Optimization

-88%

Potential reduce by 389.0 kB

  • Original 440.8 kB
  • After minification 440.5 kB
  • After compression 51.8 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. Berker.com needs all CSS files to be minified and compressed as it can save up to 389.0 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (52%)

Requests Now

23

After Optimization

11

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.berker.com

www.berker.com

816 ms

app.min.css

app.min.css

560 ms

berker.min.css

berker.min.css

286 ms

modernizr.custom.min.js

modernizr.custom.min.js

379 ms

es5-shim.min.js

es5-shim.min.js

426 ms

es5-sham.min.js

es5-sham.min.js

414 ms

polyfill.min.js

polyfill.min.js

363 ms

app.min.js

app.min.js

972 ms

additional.js

additional.js

460 ms

gtm.js

gtm.js

129 ms

header_logo_berker.png

header_logo_berker.png

535 ms

Berker-Mix_Mood_07_170522_RGB_1024x480.jpg

Berker-Mix_Mood_07_170522_RGB_1024x480.jpg

716 ms

Hager_Gebaeude_12_Shooting_Tom_G_Geb12-058_10234x480px.jpg

Hager_Gebaeude_12_Shooting_Tom_G_Geb12-058_10234x480px.jpg

649 ms

Fotolia_134193952_Subscription_1024x480px_2_final.jpg

Fotolia_134193952_Subscription_1024x480px_2_final.jpg

238 ms

ce-sans-quadrillage_1024x480px.jpg

ce-sans-quadrillage_1024x480px.jpg

199 ms

HelveticaNeueLTW05-55Roman.woff

HelveticaNeueLTW05-55Roman.woff

305 ms

MaterialIcons-Regular.woff

MaterialIcons-Regular.woff

598 ms

HelveticaNeueLTW05-75Bold.woff

HelveticaNeueLTW05-75Bold.woff

599 ms

d6d4a194.js

d6d4a194.js

488 ms

gtm.js

gtm.js

33 ms

js

js

52 ms

js

js

163 ms

web-vitals.iife.js

web-vitals.iife.js

160 ms

web-vitals.iife.js

web-vitals.iife.js

295 ms

en.js

en.js

144 ms

ajax-loader.gif

ajax-loader.gif

124 ms

berker_DS_0.jpg

berker_DS_0.jpg

287 ms

print.min.css

print.min.css

106 ms

Accessibility Review

berker.com accessibility score

67

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes do not have valid values

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

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

berker.com best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

berker.com SEO score

82

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Document doesn't have a valid hreflang

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Berker.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 Berker.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

berker.com

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