Tools & Wizards About Us
being-a-broad.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

being-a-broad.com

Savvy Tokyo - The Essential Guide for International Women and Families in Tokyo

Page Load Speed

2.1 sec in total

First Response

128 ms

Resources Loaded

1.5 sec

Page Rendered

528 ms

being-a-broad.com screenshot

About Website

Welcome to being-a-broad.com homepage info - get ready to check Being A Broad best content right away, or after learning these important things about being-a-broad.com

The Essential Guide for International Women and Families in Tokyo

Visit being-a-broad.com

Key Findings

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

Performance Metrics

being-a-broad.com performance score

0

Network Requests Diagram

being-a-broad.com

128 ms

savvytokyo.com

160 ms

main.css

304 ms

modernizr-custom.js

416 ms

styles.css

439 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Being-a-broad.com, 74% (34 requests) were made to Cdn.savvytokyo.com and 4% (2 requests) were made to Savvytokyo.com. The less responsive or slowest element that took the longest time to load (566 ms) relates to the external source Cdn.savvytokyo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 391.4 kB (19%)

Content Size

2.0 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Being-a-broad.com main page is 2.0 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. 55% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 39.5 kB

  • Original 49.1 kB
  • After minification 48.1 kB
  • After compression 9.6 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 39.5 kB or 81% of the original size.

Image Optimization

-4%

Potential reduce by 55.8 kB

  • Original 1.6 MB
  • After minification 1.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. Being A Broad images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 189.0 kB

  • Original 277.1 kB
  • After minification 275.0 kB
  • After compression 88.1 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 189.0 kB or 68% of the original size.

CSS Optimization

-83%

Potential reduce by 107.1 kB

  • Original 129.6 kB
  • After minification 128.7 kB
  • After compression 22.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. Being-a-broad.com needs all CSS files to be minified and compressed as it can save up to 107.1 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (32%)

Requests Now

38

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

being-a-broad.com

being-a-broad.com

128 ms

savvytokyo.com

savvytokyo.com

160 ms

main.css

main.css

304 ms

modernizr-custom.js

modernizr-custom.js

416 ms

styles.css

styles.css

439 ms

jquery.min.js

jquery.min.js

30 ms

jquery.form.min.js

jquery.form.min.js

416 ms

scripts.js

scripts.js

416 ms

wp-embed.min.js

wp-embed.min.js

338 ms

main.js

main.js

455 ms

video-js.min.css

video-js.min.css

114 ms

css

css

23 ms

css

css

33 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

93 ms

sdk.js

sdk.js

268 ms

savvytokyo.svg

savvytokyo.svg

175 ms

JFW-AW16-1-featured.jpg

JFW-AW16-1-featured.jpg

197 ms

school-lunch-by-Jennifer-Murawski-featured-220x124.jpg

school-lunch-by-Jennifer-Murawski-featured-220x124.jpg

178 ms

Sakura-featured-220x124.jpg

Sakura-featured-220x124.jpg

182 ms

Knives-220x124.jpg

Knives-220x124.jpg

177 ms

IMG_4906-cropped-220x124.jpg

IMG_4906-cropped-220x124.jpg

182 ms

washing-machines-220x124.jpg

washing-machines-220x124.jpg

239 ms

aw16-events-featured-790x445.jpg

aw16-events-featured-790x445.jpg

275 ms

relight-project-featured-790x445.jpg

relight-project-featured-790x445.jpg

282 ms

closet-by-Emily-May-featured-790x445.jpg

closet-by-Emily-May-featured-790x445.jpg

290 ms

kamakura-fuji-featured-790x445.jpg

kamakura-fuji-featured-790x445.jpg

290 ms

Poledancetokyo_lesson017-featured-790x445.jpg

Poledancetokyo_lesson017-featured-790x445.jpg

274 ms

pom-purin-2-featured-790x445.jpg

pom-purin-2-featured-790x445.jpg

503 ms

fashion-week-ready-featured-790x445.jpg

fashion-week-ready-featured-790x445.jpg

341 ms

IMG_6550-featured-790x445.jpg

IMG_6550-featured-790x445.jpg

354 ms

setagaya-ume-festival-featured-790x445.jpg

setagaya-ume-festival-featured-790x445.jpg

365 ms

Savvy-March-2016-featured-790x445.jpg

Savvy-March-2016-featured-790x445.jpg

328 ms

FF106-featured-790x445.jpg

FF106-featured-790x445.jpg

453 ms

davinci-cropped-380x468.jpg

davinci-cropped-380x468.jpg

421 ms

kspace.top_-300x150.jpg

kspace.top_-300x150.jpg

442 ms

analytics.js

analytics.js

33 ms

Heuristica-Regular.woff

Heuristica-Regular.woff

456 ms

Heuristica-Bold.woff

Heuristica-Bold.woff

480 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

502 ms

Heuristica-Italic.woff

Heuristica-Italic.woff

547 ms

Heuristica-BoldItalic.woff

Heuristica-BoldItalic.woff

566 ms

glyphicons-social-regular.woff

glyphicons-social-regular.woff

528 ms

collect

collect

24 ms

28 ms

xd_arbiter.php

xd_arbiter.php

214 ms

xd_arbiter.php

xd_arbiter.php

423 ms

SEO Factors

being-a-broad.com SEO score

0

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 Being-a-broad.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 Being-a-broad.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

being-a-broad.com

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