5.3 sec in total
1.4 sec
3.2 sec
720 ms
Welcome to pub.oooug.jp homepage info - get ready to check Pub Oooug best content for Japan right away, or after learning these important things about pub.oooug.jp
OpenOffice.orgとLibreOfficeに関するドキュメントを提供しています
Visit pub.oooug.jpWe analyzed Pub.oooug.jp page load time and found that the first response time was 1.4 sec and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
pub.oooug.jp performance score
name
value
score
weighting
Value2.2 s
77/100
10%
Value2.3 s
93/100
25%
Value3.6 s
87/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value2.7 s
97/100
10%
1369 ms
358 ms
358 ms
355 ms
376 ms
Our browser made a total of 47 requests to load all elements on the main page. We found that 94% of them (44 requests) were addressed to the original Pub.oooug.jp, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Static.evernote.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Pub.oooug.jp.
Page size can be reduced by 294.5 kB (47%)
622.8 kB
328.3 kB
In fact, the total size of Pub.oooug.jp main page is 622.8 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. Images take 321.2 kB which makes up the majority of the site volume.
Potential reduce by 101.9 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 101.9 kB or 86% of the original size.
Potential reduce by 70.6 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, Pub Oooug needs image optimization as it can save up to 70.6 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 114.1 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 114.1 kB or 66% of the original size.
Potential reduce by 7.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. Pub.oooug.jp needs all CSS files to be minified and compressed as it can save up to 7.9 kB or 75% of the original size.
Number of requests can be reduced by 10 (22%)
46
36
The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pub Oooug. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
pub.oooug.jp
1369 ms
style.css
358 ms
droppy.css
358 ms
l10n.js
355 ms
DD_belatedPNG_0.0.8a-min.js
376 ms
minmax.js
375 ms
jquery.js
1074 ms
jquery.droppy.js
534 ms
common.js
534 ms
styles.css
563 ms
noteit.js
380 ms
ga.js
88 ms
article-clipper.png
85 ms
img09-85x120.png
186 ms
img07-85x120.png
180 ms
img06-85x120.png
179 ms
img05-85x120.png
179 ms
img04-85x120.png
185 ms
img03-85x120.png
188 ms
img02-85x120.png
355 ms
img01-85x120.png
355 ms
img0-85x120.png
355 ms
img07-85x120.png
362 ms
img06-85x120.png
372 ms
img05-85x120.png
373 ms
img04-85x120.png
533 ms
img03-85x120.png
533 ms
img02-85x120.png
533 ms
img01-85x120.png
552 ms
img0-85x120.png
555 ms
img011-85x120.png
556 ms
img010-85x120.png
711 ms
img09-85x120.png
713 ms
img08-85x120.png
712 ms
img07-85x120.png
740 ms
img06-85x120.png
744 ms
img05-85x120.png
744 ms
img04-85x120.png
891 ms
img03-85x120.png
893 ms
img02-85x120.png
892 ms
img01-85x120.png
927 ms
img0-85x120.png
931 ms
img02-85x120.png
929 ms
search.png
1020 ms
feed_mini.png
1021 ms
__utm.gif
15 ms
print.css
189 ms
pub.oooug.jp accessibility score
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
Links do not have a discernible name
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.
pub.oooug.jp 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
pub.oooug.jp SEO score
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 doesn't use legible font sizes
Tap targets are not sized appropriately
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pub.oooug.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Pub.oooug.jp 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.
pub.oooug.jp
Open Graph description is not detected on the main page of Pub Oooug. 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: