Tools & Wizards About Us
iamhalsey.com screenshot

Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

iamhalsey.com

Halsey | Official Site

Page Load Speed

2.9 sec in total

First Response

97 ms

Resources Loaded

1.4 sec

Page Rendered

1.4 sec

iamhalsey.com screenshot

About Website

Visit iamhalsey.com now to see the best up-to-date Iam Halsey content for United States and also check out these interesting facts you probably never knew about iamhalsey.com

Sign Up For Updates

Visit iamhalsey.com

Key Findings

We analyzed Iamhalsey.com page load time and found that the first response time was 97 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

iamhalsey.com performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

31/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

10/100

25%

SI (Speed Index)

Value3.6 s

86/100

10%

TBT (Total Blocking Time)

Value610 ms

48/100

30%

CLS (Cumulative Layout Shift)

Value0.016

100/100

15%

TTI (Time to Interactive)

Value5.9 s

65/100

10%

Network Requests Diagram

iamhalsey.com

97 ms

pre_tumblelog.js

39 ms

css

46 ms

modernizr.js

35 ms

precrafted-social.css

37 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Iamhalsey.com, 26% (16 requests) were made to Assets.tumblr.com and 15% (9 requests) were made to Static.tumblr.com. The less responsive or slowest element that took the longest time to load (395 ms) relates to the external source Fonts.gstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.0 MB (18%)

Content Size

11.1 MB

After Optimization

9.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Iamhalsey.com main page is 11.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. 85% 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 8.3 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 59.3 kB

  • Original 72.1 kB
  • After minification 66.5 kB
  • After compression 12.8 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 59.3 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 29.5 kB

  • Original 8.3 MB
  • After minification 8.3 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. Iam Halsey images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 1.7 MB

  • Original 2.4 MB
  • After minification 2.4 MB
  • After compression 761.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 1.7 MB or 69% of the original size.

CSS Optimization

-76%

Potential reduce by 209.4 kB

  • Original 275.5 kB
  • After minification 270.5 kB
  • After compression 66.1 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. Iamhalsey.com needs all CSS files to be minified and compressed as it can save up to 209.4 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (58%)

Requests Now

57

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

iamhalsey.com

iamhalsey.com

97 ms

pre_tumblelog.js

pre_tumblelog.js

39 ms

css

css

46 ms

modernizr.js

modernizr.js

35 ms

precrafted-social.css

precrafted-social.css

37 ms

gobig-styles.css

gobig-styles.css

37 ms

tumblelog_post_message_queue.js

tumblelog_post_message_queue.js

42 ms

stylesheet.css

stylesheet.css

138 ms

jquery.min.js

jquery.min.js

42 ms

bit_widget.js

bit_widget.js

194 ms

gobig-plugins.js

gobig-plugins.js

193 ms

gobig-app.js

gobig-app.js

40 ms

conversion.js

conversion.js

21 ms

oct.js

oct.js

193 ms

index.js

index.js

188 ms

tumblr_o28bz5l0br1rq93oso1_500.jpg

tumblr_o28bz5l0br1rq93oso1_500.jpg

267 ms

like_iframe.html

like_iframe.html

247 ms

tumblr_n5z8zz8LBE1r1vm5vo1_500.jpg

tumblr_n5z8zz8LBE1r1vm5vo1_500.jpg

316 ms

tumblr_o279jb9iJB1udc0m0

tumblr_o279jb9iJB1udc0m0

253 ms

tumblr_nylwx9zV8w1uykvm9o1_500.gif

tumblr_nylwx9zV8w1uykvm9o1_500.gif

268 ms

tumblr_o05hbekxOG1r8mlamo1_500.jpg

tumblr_o05hbekxOG1r8mlamo1_500.jpg

276 ms

tumblr_n2c2yknjNT1smsebso1_500.jpg

tumblr_n2c2yknjNT1smsebso1_500.jpg

232 ms

tumblr_o1j4btVgfI1trmc4jo1_500.jpg

tumblr_o1j4btVgfI1trmc4jo1_500.jpg

283 ms

tumblr_o1j4btVgfI1trmc4jo2_500.jpg

tumblr_o1j4btVgfI1trmc4jo2_500.jpg

285 ms

tumblr_o23h3pjm4m1tdx274o1_500.jpg

tumblr_o23h3pjm4m1tdx274o1_500.jpg

245 ms

tumblr_o1uczgVtkF1thcdsgo1_500.png

tumblr_o1uczgVtkF1thcdsgo1_500.png

259 ms

tumblr_nbm2ofJl1W1s028jho1_500.jpg

tumblr_nbm2ofJl1W1s028jho1_500.jpg

247 ms

tumblr_muvwe9Q5Nc1sbgx0ro1_500.jpg

tumblr_muvwe9Q5Nc1sbgx0ro1_500.jpg

246 ms

tumblr_static_21adk4rxlfj4kco4c4ck8g04k.png

tumblr_static_21adk4rxlfj4kco4c4ck8g04k.png

235 ms

fixie-loader.gif

fixie-loader.gif

211 ms

dashboard.css

dashboard.css

65 ms

html5_audio_player_tlog.css

html5_audio_player_tlog.css

86 ms

index.js

index.js

93 ms

index.js

index.js

202 ms

tumblelog.js

tumblelog.js

89 ms

audio_player.js

audio_player.js

196 ms

v0SdcGFAl2aezM9Vq_aFTQ.ttf

v0SdcGFAl2aezM9Vq_aFTQ.ttf

395 ms

hbAEjbEFAEQ=

hbAEjbEFAEQ=

379 ms

precrafted-social.woff

precrafted-social.woff

379 ms

tumblr_static_c44qbmh3ancos4wwwkco04s80.jpg

tumblr_static_c44qbmh3ancos4wwwkco04s80.jpg

393 ms

tumblr_o279jb9iJB1udc0m0o1_1454886408_cover.jpg

tumblr_o279jb9iJB1udc0m0o1_1454886408_cover.jpg

84 ms

audio_player_sprite.png

audio_player_sprite.png

30 ms

229 ms

fbds.js

fbds.js

201 ms

analytics.js

analytics.js

183 ms

adsct

adsct

265 ms

adsct

adsct

212 ms

impixu

impixu

240 ms

analytics.html

analytics.html

82 ms

impixu

impixu

112 ms

login_check.html

login_check.html

35 ms

87 ms

collect

collect

37 ms

153 ms

rapid-3.33.js

rapid-3.33.js

66 ms

rapidworker-1.2.js

rapidworker-1.2.js

70 ms

ga.js

ga.js

84 ms

analytics.js

analytics.js

67 ms

cs.js

cs.js

58 ms

__utm.gif

__utm.gif

23 ms

cedexis.radar.js

cedexis.radar.js

3 ms

23 ms

Accessibility Review

iamhalsey.com accessibility score

88

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not have valid values

Best Practices

iamhalsey.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

iamhalsey.com SEO score

100

Search Engine Optimization Advices

Mobile Friendly

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

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

iamhalsey.com

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