Access fortune82.com. 포춘82

name

value

score

weighting

FCP (First Contentful Paint)

Value9.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value24.3 s

0/100

25%

SI (Speed Index)

Value21.6 s

0/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.527

14/100

15%

TTI (Time to Interactive)

Value31.8 s

0/100

10%

www.fortune82.com

1210 ms

css

31 ms

bootstrap.css

932 ms

style.css

1870 ms

dark.css

946 ms

Our browser made a total of 94 requests to load all elements on the main page. We found that 97% of them (91 requests) were addressed to the original Fortune82.com, 2% (2 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Fortune82.com.

Content Size

6.3 MB

After Optimization

4.8 MB

In fact, the total size of Fortune82.com main page is 6.3 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. 70% of websites need less resources to load. Images take 4.5 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 32.2 kB

Original 38.7 kB
After minification 36.4 kB
After compression 6.5 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 32.2 kB or 83% of the original size.

Image Optimization

-1%

Potential reduce by 53.1 kB

Original 4.5 MB
After minification 4.5 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. Fortune 82 images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 629.5 kB

Original 868.0 kB
After minification 868.0 kB
After compression 238.4 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 629.5 kB or 73% of the original size.

CSS Optimization

-87%

Potential reduce by 724.1 kB

Original 830.1 kB
After minification 669.2 kB
After compression 106.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. Fortune82.com needs all CSS files to be minified and compressed as it can save up to 724.1 kB or 87% of the original size.

Requests Now

After Optimization

The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fortune 82. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 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

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

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

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

Search Engine Optimization Advices

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

KO
Encoding

UTF-8

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

fortune82.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

포춘82

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

www.fortune82.com

css

bootstrap.css

style.css

dark.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

www.fortune82.com

css

bootstrap.css

style.css

dark.css

font-icons.css

animate.css

magnific-popup.css

et-line.css

custom.css

colors.php

fonts.css

course.css

logo2_f82.png

logo2@2x_f82.png

mb4037.jpg

mb3051.jpg

mb4036.jpg

mb5063.jpg

mb3512.jpg

mb3511.jpg

mb4509.jpg

mb3510.jpg

mb4508.jpg

mb2026.jpg

list_3043.jpg

list_3042.jpg

list_3041.jpg

list_3037.jpg

list_3036.jpg

list_5044.jpg

list_4032.jpg

list_3045.jpg

list_3044.jpg

list_4037.jpg

list_4035.jpg

list_5063.jpg

agree_001.html

privacy_002.html

jquery.js

plugins.min.js

functions.js

list_4036.jpg