5.3 sec in total
1.6 sec
3.4 sec
245 ms
Click here to check amazing Publisher content for Germany. Otherwise, check out these important facts you probably never knew about publisher.ch
Schweizer Fachzeitschrift für elektronisches Publizieren. Publikationsorgan der UGAP, User Group for Adobe Products und des ACG, Schweiz. Verband für Gestaltung am Computer.
Visit publisher.chWe analyzed Publisher.ch page load time and found that the first response time was 1.6 sec 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.
publisher.ch performance score
name
value
score
weighting
Value7.7 s
0/100
10%
Value11.7 s
0/100
25%
Value27.6 s
0/100
10%
Value1,900 ms
8/100
30%
Value0.002
100/100
15%
Value26.9 s
0/100
10%
1630 ms
461 ms
186 ms
277 ms
187 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 71% of them (55 requests) were addressed to the original Publisher.ch, 13% (10 requests) were made to Google.com and 6% (5 requests) were made to Pool.netzprojekt.ch. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Publisher.ch.
Page size can be reduced by 366.9 kB (43%)
859.6 kB
492.7 kB
In fact, the total size of Publisher.ch main page is 859.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. Images take 338.5 kB which makes up the majority of the site volume.
Potential reduce by 56.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 56.8 kB or 83% of the original size.
Potential reduce by 16.4 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. Publisher images are well optimized though.
Potential reduce by 156.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 156.8 kB or 54% of the original size.
Potential reduce by 136.9 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. Publisher.ch needs all CSS files to be minified and compressed as it can save up to 136.9 kB or 85% of the original size.
Number of requests can be reduced by 45 (63%)
72
27
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Publisher. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
publisher.ch
1630 ms
jquery.js
461 ms
swfobject.js
186 ms
config_general.css
277 ms
style.css
187 ms
downloadsubnavi.css
188 ms
downloadviewinarticle.css
271 ms
java.js
278 ms
style.css
370 ms
dmenu.css
278 ms
hmenu.css
361 ms
menu.css
367 ms
menu.js
368 ms
cssLayoutContainer.css
369 ms
java.js
453 ms
menu.css
481 ms
style.css
550 ms
bugfix.js
482 ms
browser.js
482 ms
java.js
542 ms
jquery.cycle2.all.min.js
544 ms
slide.css
557 ms
style.css
558 ms
style.css
558 ms
slimbox2.css
632 ms
fancybox.css
635 ms
slimbox2.js
637 ms
fancybox.js
728 ms
shariff.min.js
733 ms
shariff.complete.css
735 ms
mail.js
723 ms
config_editor.css
725 ms
basic.css
730 ms
logo_publisher.gif
105 ms
bg_navi_grey.gif
105 ms
rss_logo_small.gif
106 ms
imgfile7272.jpg
310 ms
imgfile7321.jpg
199 ms
imgfile7324.gif
106 ms
imgfile3016.gif
198 ms
buy.gif
197 ms
imgfile7319.gif
196 ms
imgfile7317.gif
197 ms
imgfile7192.png
385 ms
imgfile6997.png
386 ms
gtm.js
95 ms
Publink-Logo.png
295 ms
banners.fcgi
719 ms
banners.fcgi
719 ms
banners.fcgi
719 ms
cse.js
22 ms
bg_main.gif
267 ms
banners.fcgi
694 ms
cse.js
158 ms
banners.fcgi
704 ms
fancy_loading.png
213 ms
close.png
288 ms
analytics.js
24 ms
collect
12 ms
collect
55 ms
jsapi
32 ms
default+de.css
3 ms
default.css
14 ms
default+de.I.js
17 ms
default.css
38 ms
async-ads.js
76 ms
google_custom_search_watermark.gif
54 ms
small-logo.png
43 ms
search_box_icon.png
46 ms
clear.png
44 ms
nav_logo114.png
12 ms
com2publish.gif
94 ms
halbbanner.gif
283 ms
Fullsizebanner_468_60_spd_A_2016.gif
94 ms
Banner_Digitaldruckforum_2016_160x600.jpg
278 ms
B8088621.117387938;sz=160x600;ord=[timestamp]
16 ms
Banner_Digitaldruckforum_2016_160x600.jpg
186 ms
halbbanner.gif
95 ms
publisher.ch accessibility score
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
[aria-*] attributes do not match their roles
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
publisher.ch best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
publisher.ch SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
DE
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Publisher.ch can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Publisher.ch 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.
publisher.ch
Open Graph description is not detected on the main page of Publisher. 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: