Tools & Wizards About Us
zigzag.is screenshot

Report Summary

  • 73

    Performance

    Renders faster than
    82% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

zigzag.is

zigzag | A multi-disciplinary design company for innovative digital experiences

Page Load Speed

2.7 sec in total

First Response

311 ms

Resources Loaded

2.3 sec

Page Rendered

85 ms

zigzag.is screenshot

About Website

Welcome to zigzag.is homepage info - get ready to check Zigzag best content for Germany right away, or after learning these important things about zigzag.is

Zigzag is a multi-disciplinary design company for innovative digital experience. | zigzag is a multi-disciplinary design company for innovative digital experiences

Visit zigzag.is

Key Findings

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

Performance Metrics

zigzag.is performance score

73

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

79/100

10%

LCP (Largest Contentful Paint)

Value4.0 s

50/100

25%

SI (Speed Index)

Value5.5 s

55/100

10%

TBT (Total Blocking Time)

Value180 ms

92/100

30%

CLS (Cumulative Layout Shift)

Value0.039

99/100

15%

TTI (Time to Interactive)

Value7.3 s

50/100

10%

Network Requests Diagram

zigzag.is

311 ms

zigzag.is

764 ms

A.style.css,qver=6.4.5.pagespeed.cf.AGam8ipbx6.css

96 ms

A.owl.carousel.css,qv=2.pagespeed.cf.lK7VqLSisk.css

190 ms

A.style.css,qv=2.pagespeed.cf.AGam8ipbx6.css

284 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 84% of them (32 requests) were addressed to the original Zigzag.is, 8% (3 requests) were made to Use.typekit.net and 5% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (764 ms) belongs to the original domain Zigzag.is.

Page Optimization Overview & Recommendations

Page size can be reduced by 103.0 kB (4%)

Content Size

2.4 MB

After Optimization

2.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Zigzag.is 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. 35% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 40.2 kB

  • Original 52.1 kB
  • After minification 49.8 kB
  • After compression 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 40.2 kB or 77% of the original size.

Image Optimization

-2%

Potential reduce by 54.6 kB

  • Original 2.3 MB
  • After minification 2.3 MB

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. Zigzag images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 7.9 kB

  • Original 53.5 kB
  • After minification 53.5 kB
  • After compression 45.6 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 7.9 kB or 15% of the original size.

CSS Optimization

-1%

Potential reduce by 256 B

  • Original 19.2 kB
  • After minification 19.2 kB
  • After compression 19.0 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. Zigzag.is has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 5 (17%)

Requests Now

29

After Optimization

24

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

zigzag.is

zigzag.is

311 ms

zigzag.is

zigzag.is

764 ms

A.style.css,qver=6.4.5.pagespeed.cf.AGam8ipbx6.css

A.style.css,qver=6.4.5.pagespeed.cf.AGam8ipbx6.css

96 ms

A.owl.carousel.css,qv=2.pagespeed.cf.lK7VqLSisk.css

A.owl.carousel.css,qv=2.pagespeed.cf.lK7VqLSisk.css

190 ms

A.style.css,qv=2.pagespeed.cf.AGam8ipbx6.css

A.style.css,qv=2.pagespeed.cf.AGam8ipbx6.css

284 ms

jquery.min.js,qv=2.pagespeed.ce.j7j-5PzDzI.js

jquery.min.js,qv=2.pagespeed.ce.j7j-5PzDzI.js

391 ms

js

js

49 ms

mzx7obo.js

mzx7obo.js

139 ms

owl.carousel.js,qv=2.pagespeed.ce.2DtffV8QdU.js

owl.carousel.js,qv=2.pagespeed.ce.2DtffV8QdU.js

389 ms

main.js,qv=2.pagespeed.ce.QBSZKv97DE.js

main.js,qv=2.pagespeed.ce.QBSZKv97DE.js

286 ms

gtm.js

gtm.js

94 ms

zigzag_logo_nav.png.pagespeed.ce.FPAT3aLZN8.png

zigzag_logo_nav.png.pagespeed.ce.FPAT3aLZN8.png

116 ms

btn_menu.png.pagespeed.ce.lig4d2Tsi4.png

btn_menu.png.pagespeed.ce.lig4d2Tsi4.png

116 ms

btn_close-1.png.pagespeed.ce.Wtj2Xud3_B.png

btn_close-1.png.pagespeed.ce.Wtj2Xud3_B.png

117 ms

CardImage-My-BMW-App-jpg.webp

CardImage-My-BMW-App-jpg.webp

314 ms

ice-screens-cardimg.png.pagespeed.ce.o7pLhO-8EA.png

ice-screens-cardimg.png.pagespeed.ce.o7pLhO-8EA.png

612 ms

cardimg_smarte_haltestelle.png.pagespeed.ce.9KBm-CSeiT.png

cardimg_smarte_haltestelle.png.pagespeed.ce.9KBm-CSeiT.png

513 ms

cardimg_siemens_junelight.png.pagespeed.ce.fZwkto5WLN.png

cardimg_siemens_junelight.png.pagespeed.ce.fZwkto5WLN.png

519 ms

cardimg_vitaliberty_fits.png.pagespeed.ce.u853gK_RQI.png

cardimg_vitaliberty_fits.png.pagespeed.ce.u853gK_RQI.png

514 ms

cardimg_comdirect_mobox.png.pagespeed.ce.bOak4jptWJ.png

cardimg_comdirect_mobox.png.pagespeed.ce.bOak4jptWJ.png

313 ms

Photo-1-jpg.webp

Photo-1-jpg.webp

415 ms

CardImage-2.png.pagespeed.ce.V1GuQdk-pe.png

CardImage-2.png.pagespeed.ce.V1GuQdk-pe.png

517 ms

CardImage-Group-jpg.webp

CardImage-Group-jpg.webp

617 ms

clientimg_Samsung.png.pagespeed.ce.oz9hMLjonc.png

clientimg_Samsung.png.pagespeed.ce.oz9hMLjonc.png

613 ms

clientimg_Grundig.png.pagespeed.ce.HlLIZuF24g.png

clientimg_Grundig.png.pagespeed.ce.HlLIZuF24g.png

614 ms

clientimg_BMW.png.pagespeed.ce.MX837ypD7B.png

clientimg_BMW.png.pagespeed.ce.MX837ypD7B.png

616 ms

clientimg_DB.png.pagespeed.ce.FatvPjzJOf.png

clientimg_DB.png.pagespeed.ce.FatvPjzJOf.png

619 ms

clientimg_MercedesBenz.png.pagespeed.ce.MzO97Ib6NK.png

clientimg_MercedesBenz.png.pagespeed.ce.MzO97Ib6NK.png

710 ms

clientimg_comdirect.png.pagespeed.ce.DVEIpRI4Gj.png

clientimg_comdirect.png.pagespeed.ce.DVEIpRI4Gj.png

710 ms

clientimg_siemens.png.pagespeed.ce.b5y6LsdGp_.png

clientimg_siemens.png.pagespeed.ce.b5y6LsdGp_.png

711 ms

clientimg_vitaliberty.png.pagespeed.ce.HMaNEo-0vy.png

clientimg_vitaliberty.png.pagespeed.ce.HMaNEo-0vy.png

713 ms

ico_instagram_white.png.pagespeed.ce.ham0omsB-9.png

ico_instagram_white.png.pagespeed.ce.ham0omsB-9.png

714 ms

ico_linked_white.png.pagespeed.ce.o9yWZET27w.png

ico_linked_white.png.pagespeed.ce.o9yWZET27w.png

715 ms

avenirnextltpro-medium.woff

avenirnextltpro-medium.woff

720 ms

avenirnextltpro-bold.woff

avenirnextltpro-bold.woff

720 ms

d

d

25 ms

d

d

46 ms

p.gif

p.gif

39 ms

Accessibility Review

zigzag.is accessibility score

80

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

zigzag.is best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

zigzag.is SEO score

100

Search Engine Optimization Advices

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 Zigzag.is 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 Zigzag.is 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

zigzag.is

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