e-glees.com – Full Analysis


オレンジOrange | 春日井、小牧、名古屋市、グルメ、カフェ、ショップ情報サイト

(Took us an average of 6.4 seconds to load)

Table of Contents
Basic information
Whois information
Minor HTML issues found on homepage
Popular words
Pagespeed analysis
How can this website be improved?
Internal pages
Websites linked to

Basic information for e-glees.com

About: オレンジORANGEは春日井、小牧、名古屋を中心にカフェ、グルメ、ランチ、ショップ情報サイト!地域密着だから出来る情報量と皆様の日々を楽しくする情報がいっぱい!

Email or contact page: https://www.e-glees.com/contact/

Social media profiles:

Using HTTPS: Yes 🙂

Whois information

Whois Info Value
Date Registered 2012-01-01
Nameservers [‘DNS01.GMOSERVER.JP’, ‘DNS02.GMOSERVER.JP’, ‘dns02.gmoserver.jp’, ‘dns01.gmoserver.jp’]
Status ok https://icann.org/epp#ok
Email [‘[email protected]’, ‘[email protected]’, ‘[email protected]’]
Name fumiki kojima
Organization fumiki kojima
Address Anahashicho
City Kasugai-shi
State Aichi
Zipcode 486-0853
Country JP

HTML errors found on homepage

="lazy" /></div><div c
End tag “div” seen, but there were open elements.

ass="img"><a href="https://www.e-glees.com/shops/coffee-aura/"><img w
Unclosed element “a”.

グルメ</span></div><div c
End tag “div” seen, but there were open elements.

offee aura</div><div c
End tag “div” seen, but there were open elements.

End tag “div” seen, but there were open elements.

ass="img"><a href="https://www.e-glees.com/shops/umi/"><img w
Start tag “a” seen but an element of the same type was already open.

ass="img"><a href="https://www.e-glees.com/shops/umi/"><img w
No “a” element in scope but a “a” end tag seen.

="lazy" /></div><div c
End tag “div” seen, but there were open elements.

ass="img"><a href="https://www.e-glees.com/shops/umi/"><img w
Unclosed element “a”.

暮らし</span></div><div c
End tag “div” seen, but there were open elements.

Popular words

Word Frequency
esthe 2
coffee 1
aura 1
umi 1
mizuno 1
works 1
pola 1
salon 1
coco 1
dor 1
patisserie 1
petitpoire 1
pikku 1
onni 1
zoddo 1
company 1
rights 1
reserved 1

Pagespeed analysis


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

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

Defer offscreen images: Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. [Learn more](https://web.dev/offscreen-images/).
Potential savings of 42 KiB

Remove unused JavaScript: Remove unused JavaScript to reduce bytes consumed by network activity. [Learn more](https://web.dev/unused-javascript/).
Potential savings of 376 KiB

Avoid serving legacy JavaScript to modern browsers: Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren’t necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. [Learn More](https://philipwalton.com/articles/deploying-es2015-code-in-production-today/)
Potential savings of 7 KiB

Efficiently encode images: Optimized images load faster and consume less cellular data. [Learn more](https://web.dev/uses-optimized-images/).
Potential savings of 358 KiB

Properly size images: Serve images that are appropriately-sized to save cellular data and improve load time. [Learn more](https://web.dev/uses-responsive-images/).
Potential savings of 253 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 550 ms

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 18 KiB

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 828 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 90 KiB

Internal pages [TOP 20]

Website Page

External homepage links [TOP 20]

Website Page