Access lumieyes.com. [new]루미너스 아이즈 : Lumieyes !!

name

value

score

weighting

FCP (First Contentful Paint)

Value6.2 s

3/100

10%

LCP (Largest Contentful Paint)

Value8.3 s

2/100

25%

SI (Speed Index)

Value10.8 s

6/100

10%

TBT (Total Blocking Time)

Value170 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0.02

100/100

15%

TTI (Time to Interactive)

Value12.6 s

14/100

10%

lumieyes.com

892 ms

base.css

517 ms

vendor.css

872 ms

main_dev.css

874 ms

custom.css

351 ms

Our browser made a total of 98 requests to load all elements on the main page. We found that 90% of them (88 requests) were addressed to the original Lumieyes.com, 3% (3 requests) were made to Fonts.googleapis.com and 2% (2 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (6.7 sec) belongs to the original domain Lumieyes.com.

Content Size

14.8 MB

After Optimization

14.1 MB

In fact, the total size of Lumieyes.com main page is 14.8 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 13.9 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 84.2 kB

Original 98.6 kB
After minification 65.2 kB
After compression 14.4 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 33.4 kB, which is 34% 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 84.2 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 41.5 kB

Original 13.9 MB
After minification 13.8 MB

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. Lumieyes images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 292.4 kB

Original 481.4 kB
After minification 474.6 kB
After compression 189.0 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 292.4 kB or 61% of the original size.

CSS Optimization

-87%

Potential reduce by 276.5 kB

Original 317.5 kB
After minification 237.6 kB
After compression 41.0 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. Lumieyes.com needs all CSS files to be minified and compressed as it can save up to 276.5 kB or 87% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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

High

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

KO
Language Claimed

EN
Encoding

UTF-8

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

lumieyes.com

Open Graph data is detected on the main page of Lumieyes. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook:

Report Summary

Performance

Accessibility

Best Practices

SEO

[new]루미너스 아이즈 : Lumieyes !!

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

lumieyes.com

base.css

vendor.css

main_dev.css

custom.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

lumieyes.com

base.css

vendor.css

main_dev.css

custom.css

itzel.css

swiper.min.css

css

css

css

font-awesome.min.css

modernizr.js

swiper.min.js

js

jquery-2.1.3.min.js

plugins.js

main7.js

typewrite.min.js

jquery.bpopup.min.js

typewrite.min.js

nanumsquare.css

font-awesome.min.css

micons.css

fonts.css

nanumsquare.css

lumi_logo.png

ko_KR_32x24.png

en_US_32x24.png

quick-logo.png

nav_icon_01.png

nav_icon_02.png

icon_down_1.png

overlaybg.png

visual1-2.jpg

visual-tit1.png

visual4.jpg

visual-tit2.png

visual5.jpg

visual-tit3.png

visual1-3.jpg

visual-tit4.png

page.png

main_dev.css