Tools & Wizards About Us
koreyfrank.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

koreyfrank.com

koreyfrank-v2

Page Load Speed

2.7 sec in total

First Response

134 ms

Resources Loaded

2.4 sec

Page Rendered

179 ms

koreyfrank.com screenshot

About Website

Visit koreyfrank.com now to see the best up-to-date Koreyfrank content and also check out these interesting facts you probably never knew about koreyfrank.com

Amazing little snowboarder and skateboarder working hard to acheive his dreams. Korey started skating at age 3 and snowboarding at 4.

Visit koreyfrank.com

Key Findings

We analyzed Koreyfrank.com page load time and found that the first response time was 134 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

koreyfrank.com performance score

0

Network Requests Diagram

koreyfrank.com

134 ms

www.koreyfrank.com

89 ms

bt

102 ms

require.min.js

81 ms

main-r.min.js

86 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 5% of them (3 requests) were addressed to the original Koreyfrank.com, 52% (32 requests) were made to Static.parastorage.com and 26% (16 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.2 MB (72%)

Content Size

3.1 MB

After Optimization

869.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Koreyfrank.com main page is 3.1 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. 75% 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. Javascripts take 2.7 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 73.5 kB

  • Original 89.2 kB
  • After minification 89.0 kB
  • After compression 15.7 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 73.5 kB or 82% of the original size.

Image Optimization

-7%

Potential reduce by 15.7 kB

  • Original 221.5 kB
  • After minification 205.8 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. Koreyfrank images are well optimized though.

JavaScript Optimization

-77%

Potential reduce by 2.1 MB

  • Original 2.7 MB
  • After minification 2.7 MB
  • After compression 639.6 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 2.1 MB or 77% of the original size.

CSS Optimization

-84%

Potential reduce by 44.1 kB

  • Original 52.5 kB
  • After minification 49.5 kB
  • After compression 8.5 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. Koreyfrank.com needs all CSS files to be minified and compressed as it can save up to 44.1 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (74%)

Requests Now

58

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Koreyfrank. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

koreyfrank.com

koreyfrank.com

134 ms

www.koreyfrank.com

www.koreyfrank.com

89 ms

bt

bt

102 ms

require.min.js

require.min.js

81 ms

main-r.min.js

main-r.min.js

86 ms

viewer.css

viewer.css

84 ms

dynamicmodel

dynamicmodel

24 ms

8d64e9_6757ccc18ed8ea1852f498e9793d2469_100.json.z

8d64e9_6757ccc18ed8ea1852f498e9793d2469_100.json.z

457 ms

8d64e9_e756a9535aac4571b434e55f8da9a9e0_100.json.z

8d64e9_e756a9535aac4571b434e55f8da9a9e0_100.json.z

460 ms

ugc-viewer

ugc-viewer

38 ms

bt

bt

141 ms

skins.min.js

skins.min.js

143 ms

components.min.js

components.min.js

137 ms

utils.min.js

utils.min.js

71 ms

core.min.js

core.min.js

135 ms

react-with-addons.min.js

react-with-addons.min.js

136 ms

lodash.min.js

lodash.min.js

51 ms

TweenMax.min.js

TweenMax.min.js

141 ms

layout.min.js

layout.min.js

138 ms

tpa.min.js

tpa.min.js

135 ms

fonts.min.js

fonts.min.js

142 ms

animations.min.js

animations.min.js

134 ms

swfobject.min.js

swfobject.min.js

138 ms

mousetrap.min.js

mousetrap.min.js

139 ms

tweenEngine.min.js

tweenEngine.min.js

142 ms

DrawSVGPlugin.min.js

DrawSVGPlugin.min.js

139 ms

react-dom.min.js

react-dom.min.js

141 ms

ScrollToPlugin.min.js

ScrollToPlugin.min.js

142 ms

widgets.min.js

widgets.min.js

140 ms

experiment.js

experiment.js

142 ms

render.min.js

render.min.js

141 ms

wixappsCore.min.js

wixappsCore.min.js

143 ms

wixappsClassics.min.js

wixappsClassics.min.js

144 ms

wixappsBuilder.min.js

wixappsBuilder.min.js

140 ms

zepto.min.js

zepto.min.js

139 ms

color.min.js

color.min.js

139 ms

react-dom-server.min.js

react-dom-server.min.js

232 ms

bt

bt

97 ms

latin.css

latin.css

369 ms

dc.js

dc.js

51 ms

bt

bt

38 ms

bt

bt

276 ms

fe977a575a81f1ee29d71683f1694c29.wix_mp

fe977a575a81f1ee29d71683f1694c29.wix_mp

213 ms

f0df5d7bcea0d0c539ea722e8dbc4222.wix_mp

f0df5d7bcea0d0c539ea722e8dbc4222.wix_mp

252 ms

40ead80809414e4509d0fcf31d95a0d1.wix_mp

40ead80809414e4509d0fcf31d95a0d1.wix_mp

185 ms

e2a661042011d293f8ca380c25898600.wix_mp

e2a661042011d293f8ca380c25898600.wix_mp

405 ms

8d64e9_070eb0018bb84a67ae914cf6a2ec9c54.jpg

8d64e9_070eb0018bb84a67ae914cf6a2ec9c54.jpg

420 ms

8d64e9_9ae48918bd05f4c8aee72114062ec318.png

8d64e9_9ae48918bd05f4c8aee72114062ec318.png

297 ms

8d64e9_2206f5a59ff0457f19fc585753903177.png

8d64e9_2206f5a59ff0457f19fc585753903177.png

563 ms

8d64e9_d146573fa23739c8954ac1b4bb331f47.png

8d64e9_d146573fa23739c8954ac1b4bb331f47.png

370 ms

729a173eaae0e4803548a358b2d3edd6.wix_mp

729a173eaae0e4803548a358b2d3edd6.wix_mp

551 ms

8d64e9_339dbc1bf4f3274c09bea9e8718ee5a0.png

8d64e9_339dbc1bf4f3274c09bea9e8718ee5a0.png

588 ms

8d64e9_d4b0b792a1384f058df98c3e454fc181.png

8d64e9_d4b0b792a1384f058df98c3e454fc181.png

659 ms

8d64e9_597da072c37f48a88db6a85b22da9d98.png

8d64e9_597da072c37f48a88db6a85b22da9d98.png

1195 ms

8d64e9_e70d1c26ad7896c5ee1fd7877e0b2d60.png

8d64e9_e70d1c26ad7896c5ee1fd7877e0b2d60.png

665 ms

8d64e9_1350bd779ec50ebcf108674fd68d0925.png

8d64e9_1350bd779ec50ebcf108674fd68d0925.png

682 ms

bt

bt

89 ms

bt

bt

90 ms

__utm.gif

__utm.gif

28 ms

opensans-bold-webfont.woff

opensans-bold-webfont.woff

7 ms

opensans-regular-webfont.woff

opensans-regular-webfont.woff

27 ms

ugc-viewer

ugc-viewer

37 ms

SEO Factors

koreyfrank.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Koreyfrank.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Koreyfrank.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

koreyfrank.com

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