Tools & Wizards About Us
templates.openoffice.org screenshot

Report Summary

  • 70

    Performance

    Renders faster than
    81% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 54

    SEO

    Google-friendlier than
    19% of websites

templates.openoffice.org

Apache OpenOffice Templates

Page Load Speed

13.4 sec in total

First Response

6.3 sec

Resources Loaded

6.9 sec

Page Rendered

169 ms

templates.openoffice.org screenshot

About Website

Click here to check amazing Templates Open Office content for United States. Otherwise, check out these important facts you probably never knew about templates.openoffice.org

Visit templates.openoffice.org

Key Findings

We analyzed Templates.openoffice.org page load time and found that the first response time was 6.3 sec and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

templates.openoffice.org performance score

70

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

46/100

25%

SI (Speed Index)

Value6.5 s

39/100

10%

TBT (Total Blocking Time)

Value160 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0.075

95/100

15%

TTI (Time to Interactive)

Value4.9 s

77/100

10%

Network Requests Diagram

templates.openoffice.org

6337 ms

system.base.css

56 ms

feature_media.css

57 ms

field.css

55 ms

lineage_select.css

59 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 92% of them (67 requests) were addressed to the original Templates.openoffice.org, 3% (2 requests) were made to Fonts.googleapis.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (6.3 sec) belongs to the original domain Templates.openoffice.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 537.8 kB (74%)

Content Size

731.2 kB

After Optimization

193.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Templates.openoffice.org main page is 731.2 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. 35% of websites need less resources to load. Javascripts take 327.4 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 46.9 kB

  • Original 54.7 kB
  • After minification 51.1 kB
  • After compression 7.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 46.9 kB or 86% of the original size.

Image Optimization

-13%

Potential reduce by 7.4 kB

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

JavaScript Optimization

-71%

Potential reduce by 233.9 kB

  • Original 327.4 kB
  • After minification 265.6 kB
  • After compression 93.5 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 233.9 kB or 71% of the original size.

CSS Optimization

-85%

Potential reduce by 249.7 kB

  • Original 293.1 kB
  • After minification 241.2 kB
  • After compression 43.4 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. Templates.openoffice.org needs all CSS files to be minified and compressed as it can save up to 249.7 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 54 (77%)

Requests Now

70

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Templates 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 31 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

templates.openoffice.org

templates.openoffice.org

6337 ms

system.base.css

system.base.css

56 ms

feature_media.css

feature_media.css

57 ms

field.css

field.css

55 ms

lineage_select.css

lineage_select.css

59 ms

mollom.css

mollom.css

55 ms

views.css

views.css

68 ms

chosen.css

chosen.css

82 ms

chosen-drupal.css

chosen-drupal.css

89 ms

colorbox_style.css

colorbox_style.css

86 ms

ctools.css

ctools.css

90 ms

feature_pages.css

feature_pages.css

91 ms

locale.css

locale.css

94 ms

search_api_autocomplete.css

search_api_autocomplete.css

113 ms

fivestar.css

fivestar.css

110 ms

fonawesome-star.css

fonawesome-star.css

112 ms

style.css

style.css

240 ms

inline_entity_form.css

inline_entity_form.css

115 ms

commerce-backoffice.css

commerce-backoffice.css

123 ms

media.css

media.css

137 ms

flexslider.css

flexslider.css

139 ms

date.css

date.css

142 ms

flexslider_img.css

flexslider_img.css

142 ms

font-awesome.css

font-awesome.css

173 ms

css

css

24 ms

css

css

36 ms

jquery.min.js

jquery.min.js

215 ms

jquery.once.js

jquery.once.js

165 ms

drupal.js

drupal.js

168 ms

states.js

states.js

169 ms

zh-hans_ZxvVD9JZdW9P0ztozeXYe1PBC7wasdD1lJeC2hsVhpQ.js

zh-hans_ZxvVD9JZdW9P0ztozeXYe1PBC7wasdD1lJeC2hsVhpQ.js

196 ms

chosen.jquery.min.js

chosen.jquery.min.js

198 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

199 ms

colorbox.js

colorbox.js

201 ms

colorbox_style.js

colorbox_style.js

223 ms

autocomplete.js

autocomplete.js

224 ms

search_api_autocomplete.js

search_api_autocomplete.js

227 ms

fivestar.js

fivestar.js

229 ms

googleanalytics.js

googleanalytics.js

250 ms

facetapi.js

facetapi.js

238 ms

affix.js

affix.js

237 ms

alert.js

alert.js

239 ms

button.js

button.js

239 ms

carousel.js

carousel.js

237 ms

collapse.js

collapse.js

229 ms

dropdown.js

dropdown.js

210 ms

modal.js

modal.js

209 ms

tooltip.js

tooltip.js

211 ms

popover.js

popover.js

206 ms

scrollspy.js

scrollspy.js

214 ms

tab.js

tab.js

230 ms

transition.js

transition.js

215 ms

states.js

states.js

212 ms

autocomplete.js

autocomplete.js

215 ms

chosen.js

chosen.js

212 ms

bootstrap.js

bootstrap.js

289 ms

analytics.js

analytics.js

23 ms

collect

collect

91 ms

logo.svg

logo.svg

144 ms

fid_16176_thumbnail.png

fid_16176_thumbnail.png

150 ms

bg-gray-pixel.png

bg-gray-pixel.png

143 ms

fid_16820_thumbnail.png

fid_16820_thumbnail.png

148 ms

fid_20128_thumbnail.png

fid_20128_thumbnail.png

148 ms

fid_15364_thumbnail.png

fid_15364_thumbnail.png

148 ms

fid_15977_thumbnail.png

fid_15977_thumbnail.png

170 ms

fid_22103_thumbnail.png

fid_22103_thumbnail.png

171 ms

fid_14269_thumbnail.png

fid_14269_thumbnail.png

174 ms

fid_15571_thumbnail.png

fid_15571_thumbnail.png

175 ms

apache.png

apache.png

171 ms

sourceforge.png

sourceforge.png

174 ms

2UX7WLTfW3W8TclTUvlFyQ.woff

2UX7WLTfW3W8TclTUvlFyQ.woff

31 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

76 ms

zhcz-_WihjSQC0oHJ9TCYBsxEYwM7FgeyaSgU71cLG0.woff

zhcz-_WihjSQC0oHJ9TCYBsxEYwM7FgeyaSgU71cLG0.woff

44 ms

Accessibility Review

templates.openoffice.org accessibility score

77

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

templates.openoffice.org best practices score

75

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

templates.openoffice.org SEO score

54

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    ZH

  • Encoding

    UTF-8

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

templates.openoffice.org

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