Tools & Wizards About Us
1601.com screenshot

Report Summary

  • 69

    Performance

    Renders faster than
    81% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 87% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

1601.com

Kommunikationsagentur/Werbeagentur in Erlangen - Werbeagentur 1601.com

Page Load Speed

4.8 sec in total

First Response

334 ms

Resources Loaded

4.2 sec

Page Rendered

220 ms

1601.com screenshot

About Website

Welcome to 1601.com homepage info - get ready to check 1601 best content right away, or after learning these important things about 1601.com

1601.communication bietet Onlinemarketing in allen Facetten: Webdesign & Webentwicklung im CMS Contao, SEO für Google und andere Suchmaschinen, gedruckte Werbemittel und Hosting.

Visit 1601.com

Key Findings

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

Performance Metrics

1601.com performance score

69

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

42/100

25%

SI (Speed Index)

Value5.3 s

58/100

10%

TBT (Total Blocking Time)

Value230 ms

87/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value4.6 s

81/100

10%

Network Requests Diagram

1601.com

334 ms

453 ms

639bbdf92e6c.css

620 ms

jquery-1.11.0.min.js

23 ms

eb9ff6b57bbf.js

634 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that 41% of them (9 requests) were addressed to the original 1601.com, 32% (7 requests) were made to Www-static-files.1601.com and 9% (2 requests) were made to Www-static-assets.1601.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Www-static-files.1601.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 67.8 kB (1%)

Content Size

5.4 MB

After Optimization

5.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 1601.com main page is 5.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 5.3 MB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 10.4 kB

  • Original 14.2 kB
  • After minification 13.2 kB
  • After compression 3.8 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 10.4 kB or 73% of the original size.

Image Optimization

-0%

Potential reduce by 9.7 kB

  • Original 5.3 MB
  • After minification 5.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. 1601 images are well optimized though.

JavaScript Optimization

-57%

Potential reduce by 41.2 kB

  • Original 72.0 kB
  • After minification 72.0 kB
  • After compression 30.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 41.2 kB or 57% of the original size.

CSS Optimization

-74%

Potential reduce by 6.4 kB

  • Original 8.6 kB
  • After minification 7.0 kB
  • After compression 2.2 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. 1601.com needs all CSS files to be minified and compressed as it can save up to 6.4 kB or 74% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (16%)

Requests Now

19

After Optimization

16

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

1601.com

1601.com

334 ms

453 ms

639bbdf92e6c.css

639bbdf92e6c.css

620 ms

jquery-1.11.0.min.js

jquery-1.11.0.min.js

23 ms

eb9ff6b57bbf.js

eb9ff6b57bbf.js

634 ms

default.css

default.css

322 ms

css

css

52 ms

default.js

default.js

330 ms

ga.js

ga.js

75 ms

1601_classic_STER.jpg

1601_classic_STER.jpg

1450 ms

units2015.png

units2015.png

427 ms

1601_interactive_CTS.jpg

1601_interactive_CTS.jpg

1446 ms

1601_classic_STERJU.jpg

1601_classic_STERJU.jpg

1909 ms

1601_interactive_HW.jpg

1601_interactive_HW.jpg

2131 ms

1601_interactive_UFSK.jpg

1601_interactive_UFSK.jpg

2114 ms

Juwelier-Winnebeck-Mailing.jpg

Juwelier-Winnebeck-Mailing.jpg

1162 ms

Druckhaus-Haspel-Erlangen-Weihnachtsmailing.jpg

Druckhaus-Haspel-Erlangen-Weihnachtsmailing.jpg

2153 ms

arrow.png

arrow.png

325 ms

logo.png

logo.png

333 ms

circle.png

circle.png

329 ms

DINWeb-Medium.woff

DINWeb-Medium.woff

442 ms

__utm.gif

__utm.gif

11 ms

Accessibility Review

1601.com accessibility score

95

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

Links do not have a discernible name

Best Practices

1601.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

SEO Factors

1601.com SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 1601.com can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that 1601.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

1601.com

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