- cthistoricgardens.org – Full Analysis - April 24, 2021
- hawaiimediation.org – Full Analysis - April 24, 2021
- Cultural Corridor (culturalcorridor.org) – Full Analysis - April 24, 2021
(Took us an average of 1.1 seconds to load)
|Table of Contents|
|Minor HTML issues found on homepage|
|How can this website be improved?|
|Websites linked to|
Basic information for nakamurashoten.co.jp
Email or contact page: https://nakamurashoten.co.jp/contact.html
Social media profiles:
Using HTTPS: Yes 🙂
HTML errors found on homepage
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html
Almost standards mode doctype. Expected “”.
UTF-8" /><meta http-equiv="Content-Style-Type" content="text/css" /><meta
Bad value “Content-Style-Type” for attribute “http-equiv” on element “meta”.
Bad value “Content-Script-Type” for attribute “http-equiv” on element “meta”.
"><title>æ ªå¼ä¼ç¤¾ ä¸æå
Forbidden code point U+008f.
<title>æ ªå¼ä¼ç¤¾ ä¸æåå
Forbidden code point U+009a.
Forbidden code point U+009d.
Forbidden code point U+0091.
Forbidden code point U+0095.
Forbidden code point U+0086.
Forbidden code point U+0097.
OVERALL SITE SPEED: AVERAGE (details below)
CUMULATIVE LAYOUT SHIFT SCORE: AVERAGE. Have you ever been reading an article online when something suddenly changes on the page? Without warning, the text moves, and you’ve lost your place. Or even worse: you’re about to tap a link or a button, but in the instant before your finger landsâ€”BOOMâ€”the link moves, and you end up clicking something else! This is a measure of how often this is happening on your website.
FIRST CONTENTFUL PAINT MS SCORE: AVERAGE. This measures the time taken for the first thing on your website to load when a visitor goes there.
FIRST INPUT DELAY MS SCORE: AVERAGE. How long it takes for your website to react if the user interacts with it in some way, such as clicking a link or button.
LARGEST CONTENTFUL PAINT MS SCORE: AVERAGE. Measures how long the main part of the website takes to load.
Opportunities for improvement
Minify CSS: Minifying CSS files can reduce network payload sizes. [Learn more](https://web.dev/unminified-css/).
Potential savings of 4 KiB
Remove unused CSS: Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. [Learn more](https://web.dev/unused-css-rules/).
Potential savings of 15 KiB
Enable text compression: Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. [Learn more](https://web.dev/uses-text-compression/).
Potential savings of 21 KiB
Avoid multiple page redirects: Redirects introduce additional delays before the page can be loaded. [Learn more](https://web.dev/redirects/).
Potential savings of 230 ms
Serve images in next-gen formats: Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. [Learn more](https://web.dev/uses-webp-images/).
Potential savings of 966 KiB
Potential savings of 39 KiB
Potential savings of 49 KiB
Eliminate render-blocking resources: Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. [Learn more](https://web.dev/render-blocking-resources/).
Potential savings of 480 ms
Internal pages [TOP 20]
External homepage links [TOP 20]