6.5 sec in total
518 ms
5.8 sec
179 ms
Welcome to weisang.com homepage info - get ready to check Weisang best content for Ukraine right away, or after learning these important things about weisang.com
Passgenaue Software- und Engineering-Lösungen für Ihre Messdatenauswertung bei WEISANG. ✓Innovativ ✓Individuell →WEISANG. Jetzt informieren!
Visit weisang.comWe analyzed Weisang.com page load time and found that the first response time was 518 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
weisang.com performance score
name
value
score
weighting
Value9.2 s
0/100
10%
Value13.8 s
0/100
25%
Value20.2 s
0/100
10%
Value1,520 ms
13/100
30%
Value0.24
52/100
15%
Value19.9 s
2/100
10%
518 ms
337 ms
122 ms
196 ms
200 ms
Our browser made a total of 39 requests to load all elements on the main page. We found that 95% of them (37 requests) were addressed to the original Weisang.com, 3% (1 request) were made to Ajax.googleapis.com and 3% (1 request) were made to Stats.weisang.com. The less responsive or slowest element that took the longest time to load (662 ms) relates to the external source Stats.weisang.com.
Page size can be reduced by 273.3 kB (37%)
737.7 kB
464.4 kB
In fact, the total size of Weisang.com main page is 737.7 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. 30% of websites need less resources to load. Images take 360.4 kB which makes up the majority of the site volume.
Potential reduce by 13.6 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 2.0 kB, which is 11% 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 13.6 kB or 76% of the original size.
Potential reduce by 21.2 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. Weisang images are well optimized though.
Potential reduce by 170.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 170.8 kB or 62% of the original size.
Potential reduce by 67.5 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. Weisang.com needs all CSS files to be minified and compressed as it can save up to 67.5 kB or 82% of the original size.
Number of requests can be reduced by 21 (57%)
37
16
The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Weisang. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
weisang.com
518 ms
337 ms
stylesheet_7e1c5aa6a0.1423141816.css
122 ms
include.1423141823.css
196 ms
powermail.1423141823.css
200 ms
javascript_26e79dba8d.1423141817.js
198 ms
slightbox.css
199 ms
prototype.1.7.0.yui.js
488 ms
scriptaculous.js
218 ms
lightbox.2.0.5.yui.js
287 ms
jquery.min.js
5 ms
plugin.js
384 ms
common.js
291 ms
javascript_f3d2f34e53.1423141818.js
292 ms
blueprint.css
123 ms
typo3-csc.css
195 ms
typo3-ext.css
200 ms
common.css
202 ms
project.css
221 ms
nav_menu.css
291 ms
debug.css
293 ms
effects.js
108 ms
builder.js
106 ms
grid.png
100 ms
logo.png
107 ms
search.png
106 ms
bg_searchButton.gif
101 ms
rss_icon.png
103 ms
arrow_blue.png
100 ms
bg_top_nav.png
197 ms
weisang-flexpro10-new-release.png
585 ms
flexpro10-button-features.png
199 ms
clear.gif
201 ms
Richard-Weisang-Weisang-GmbH.png
204 ms
teaser_18.png
205 ms
teaser_12.png
294 ms
arrow_grey_up.png
299 ms
piwik.js
662 ms
print.1423141823.css
99 ms
weisang.com 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 input fields do not have accessible names
[role]s are not contained by their required parent element
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
Buttons do not have an accessible name
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
weisang.com 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
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
weisang.com SEO score
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
Tap targets are not sized appropriately
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Weisang.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 Weisang.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.
weisang.com
Open Graph description is not detected on the main page of Weisang. 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: