2.9 sec in total
153 ms
2.5 sec
250 ms
Visit suse.com now to see the best up-to-date SUSE content for China and also check out these interesting facts you probably never knew about suse.com
Modernize your infrastructure with SUSE Linux Enterprise servers, cloud technology for IaaS, and SUSE's software-defined storage.
Visit suse.comWe analyzed Suse.com page load time and found that the first response time was 153 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
suse.com performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value25.9 s
0/100
25%
Value10.3 s
8/100
10%
Value1,790 ms
10/100
30%
Value0.094
91/100
15%
Value23.5 s
1/100
10%
153 ms
579 ms
191 ms
322 ms
232 ms
Our browser made a total of 113 requests to load all elements on the main page. We found that 54% of them (61 requests) were addressed to the original Suse.com, 7% (8 requests) were made to and 5% (6 requests) were made to Dev.visualwebsiteoptimizer.com. The less responsive or slowest element that took the longest time to load (623 ms) relates to the external source Re.sajari.com.
Page size can be reduced by 1.4 MB (46%)
3.0 MB
1.6 MB
In fact, the total size of Suse.com main page is 3.0 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. 60% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 180.5 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 27.5 kB, which is 12% 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 180.5 kB or 81% of the original size.
Potential reduce by 314.9 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. Obviously, SUSE needs image optimization as it can save up to 314.9 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 551.3 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 551.3 kB or 68% of the original size.
Potential reduce by 341.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. Suse.com needs all CSS files to be minified and compressed as it can save up to 341.2 kB or 53% of the original size.
Number of requests can be reduced by 55 (56%)
99
44
The browser has sent 99 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SUSE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and as a result speed up the page load time.
suse.com
153 ms
www.suse.com
579 ms
fonts.css
191 ms
322 ms
232 ms
universal_analytics.js
182 ms
home.js
183 ms
gtm.js
35 ms
107 ms
834A38E61C6EBEFF6.css
204 ms
170 ms
analytics.js
91 ms
di.js
179 ms
N52iZFMl.min.js
166 ms
j.php
124 ms
chat-image3.png
85 ms
SUSE_25_Year_Logo.svg
369 ms
localization.png
84 ms
sapglobalpartner.png
84 ms
wright-flood-logo.png
157 ms
S2-logo.png
158 ms
SuseHot-1.jpg
158 ms
SuseHot-2.jpg
256 ms
SuseHot-3.jpg
258 ms
Suse-hotoffer-webinar.jpg
256 ms
fn-fbook-ico.png
255 ms
fn-twit-ico.png
257 ms
fn-link-ico.png
332 ms
fn-goog-ico.png
331 ms
fn-suse-ico.png
332 ms
product-icon-sles.png
331 ms
mission-critical.png
332 ms
product-icon-osc02.png
413 ms
product-icon-stor02.png
413 ms
product-icon-sap.png
413 ms
product-icon-man02.png
414 ms
form.php
391 ms
green.png
409 ms
navy.png
446 ms
xODr+T8hcETzya
24 ms
AvQLPJY=
25 ms
p4ffSfkLkq08fg==
24 ms
zLMtjeubZhdRPcijTR7wyOCZQMfej+mxoJAo2nNqrN3QVxoEy+ONxUZQx9I2kqYz93yE43NNM0CFteA2ctMzovOuc9ELykY1PyvQx6XE149P7nfZ3evydVL8AllQ8vg==
23 ms
IXBE88mg==
22 ms
v5Pg7KX8C9As8lg==
21 ms
FsHhjmeCDnnDG5CsZcHnXeeUr5Qc2fikSB+THlYzPr3feX+nh99J+QuSrTx+
21 ms
J1UvwCWVDy+
21 ms
280 ms
caas-platform-banner.png
425 ms
carousel_btn_left.png
424 ms
carousel_btn_right.png
421 ms
fontawesome-webfont.woff
509 ms
tab_pane2_graphic1.png
412 ms
tab_pane2_graphic2.png
452 ms
tab_pane2_graphic3.png
451 ms
navy_notch.png
449 ms
90-seconds.png
505 ms
video-teaser-bg.png
486 ms
manager-chalktalk.png
547 ms
storage.png
544 ms
green_play.png
503 ms
live.js
499 ms
bat.js
247 ms
sj.js
276 ms
collect
55 ms
amazon.png
497 ms
v.gif
127 ms
va-31fcb4ba28c8bf31213652a5ff92f00c.js
123 ms
track-31fcb4ba28c8bf31213652a5ff92f00c.js
122 ms
opa-853ef9b6f28eaf8557515c4b0187f093.js
174 ms
cisco.png
457 ms
dell.png
473 ms
fujitsu.png
472 ms
pixel
249 ms
hitachi.png
499 ms
store
539 ms
svrGP.aspx
264 ms
tracking.js
162 ms
ect.html
190 ms
elqCfg.min.js
209 ms
369 ms
heap-3782239331.js
201 ms
470 ms
hp.png
422 ms
ibm.png
423 ms
intel.png
425 ms
lenovo.png
425 ms
102 ms
ms.png
386 ms
sap.png
398 ms
sgi.png
399 ms
vmware.png
402 ms
worker-9819a2aaa362b1e381bdc9edc9e855dc.js
57 ms
ga-audiences
76 ms
ip.json
180 ms
pixel
46 ms
get_dynamic_config.js
143 ms
gotham-book.woff
328 ms
svrGP
170 ms
h
96 ms
svrGP.aspx
168 ms
get_static_config.3.1152.4.4.431.66.63.47.19.3.3.2.2.js
87 ms
collect
22 ms
index.php
222 ms
68 ms
localization.en.3.06a3584c688737c3e35f4146584405cf_fee7c342b3dd9ad655c7010dd49e1c59.js
109 ms
ping
94 ms
re.sajari.com
623 ms
sj.css
521 ms
47 ms
6 ms
16 ms
collect
3 ms
suse.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-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Links do not have a discernible name
suse.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
Missing source maps for large first-party JavaScript
suse.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Suse.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 Suse.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.
suse.com
Open Graph description is not detected on the main page of SUSE. 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: