Tools & Wizards About Us
no.openoffice.org screenshot

Report Summary

  • 85

    Performance

    Renders faster than
    88% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

no.openoffice.org

Apache OpenOffice - Offisielt nettsted - Den frie og åpne kontorpakken

Page Load Speed

1.4 sec in total

First Response

242 ms

Resources Loaded

1.1 sec

Page Rendered

78 ms

no.openoffice.org screenshot

About Website

Visit no.openoffice.org now to see the best up-to-date No Open Office content for United States and also check out these interesting facts you probably never knew about no.openoffice.org

Offisiell hjemmeside for Apache OpenOffice åpen kildekode prosjekt, hjemme til OpenOffice Writer, Calc, Impress, Draw og Base.

Visit no.openoffice.org

Key Findings

We analyzed No.openoffice.org page load time and found that the first response time was 242 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

no.openoffice.org performance score

85

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

71/100

25%

SI (Speed Index)

Value3.5 s

89/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value3.2 s

94/100

10%

Network Requests Diagram

no.openoffice.org

242 ms

211 ms

ooo.css

103 ms

globalvars.js

204 ms

msg_prop_l10n.js

205 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original No.openoffice.org, 88% (22 requests) were made to Openoffice.org and 4% (1 request) were made to Apachecon.com. The less responsive or slowest element that took the longest time to load (358 ms) relates to the external source Openoffice.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 41.3 kB (35%)

Content Size

117.0 kB

After Optimization

75.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of No.openoffice.org main page is 117.0 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. 25% of websites need less resources to load. Images take 42.3 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 21.0 kB

  • Original 28.1 kB
  • After minification 24.5 kB
  • After compression 7.1 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 3.6 kB, which is 13% 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 21.0 kB or 75% of the original size.

Image Optimization

-19%

Potential reduce by 7.9 kB

  • Original 42.3 kB
  • After minification 34.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. Obviously, No Open Office needs image optimization as it can save up to 7.9 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-40%

Potential reduce by 8.9 kB

  • Original 22.2 kB
  • After minification 22.2 kB
  • After compression 13.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 8.9 kB or 40% of the original size.

CSS Optimization

-14%

Potential reduce by 3.5 kB

  • Original 24.3 kB
  • After minification 24.3 kB
  • After compression 20.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. No.openoffice.org needs all CSS files to be minified and compressed as it can save up to 3.5 kB or 14% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (30%)

Requests Now

23

After Optimization

16

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

no.openoffice.org

no.openoffice.org

242 ms

211 ms

ooo.css

ooo.css

103 ms

globalvars.js

globalvars.js

204 ms

msg_prop_l10n.js

msg_prop_l10n.js

205 ms

languages.js

languages.js

205 ms

download.js

download.js

207 ms

home.css

home.css

206 ms

styles.css

styles.css

358 ms

exceptions.css

exceptions.css

305 ms

snippet.js

snippet.js

20 ms

valid-xhtml10-blue.png

valid-xhtml10-blue.png

42 ms

AOO4_website_logo.png

AOO4_website_logo.png

103 ms

logo-rss-16.png

logo-rss-16.png

104 ms

logo-facebook-16.png

logo-facebook-16.png

106 ms

logo-twitter-16.png

logo-twitter-16.png

106 ms

logo-youtube-16.png

logo-youtube-16.png

106 ms

asf_logo_small.png

asf_logo_small.png

120 ms

action-info.png

action-info.png

181 ms

action-download.png

action-download.png

170 ms

action-help.png

action-help.png

172 ms

action-extend.png

action-extend.png

172 ms

action-participate.png

action-participate.png

171 ms

action-social.png

action-social.png

204 ms

campaign-divider.png

campaign-divider.png

270 ms

Accessibility Review

no.openoffice.org accessibility score

89

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

no.openoffice.org best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

no.openoffice.org SEO score

69

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise No.openoffice.org can be misinterpreted by Google and other search engines. Our service has detected that English 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 No.openoffice.org 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

no.openoffice.org

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