2.1 sec in total
64 ms
1.6 sec
405 ms
Welcome to storyworldwide.com homepage info - get ready to check Story Worldwide best content for United States right away, or after learning these important things about storyworldwide.com
Visit storyworldwide.comWe analyzed Storyworldwide.com page load time and found that the first response time was 64 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 40% of websites can load faster.
storyworldwide.com performance score
name
value
score
weighting
Value2.2 s
78/100
10%
Value7.3 s
4/100
25%
Value7.0 s
33/100
10%
Value2,030 ms
7/100
30%
Value0.798
5/100
15%
Value11.1 s
20/100
10%
64 ms
383 ms
13 ms
16 ms
257 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 61% of them (48 requests) were addressed to the original Storyworldwide.com, 14% (11 requests) were made to Maps.googleapis.com and 9% (7 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (383 ms) belongs to the original domain Storyworldwide.com.
Page size can be reduced by 775.6 kB (38%)
2.1 MB
1.3 MB
In fact, the total size of Storyworldwide.com main page is 2.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. 70% of websites need less resources to load. Javascripts take 960.9 kB which makes up the majority of the site volume.
Potential reduce by 37.3 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 11.9 kB, which is 26% 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 37.3 kB or 81% of the original size.
Potential reduce by 0 B
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. Story Worldwide images are well optimized though.
Potential reduce by 669.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 669.1 kB or 70% of the original size.
Potential reduce by 69.2 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. Storyworldwide.com needs all CSS files to be minified and compressed as it can save up to 69.2 kB or 75% of the original size.
Number of requests can be reduced by 32 (48%)
66
34
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Story Worldwide. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
storyworldwide.com
64 ms
www.storyworldwide.com
383 ms
wp-emoji-release.min.js
13 ms
modernizr.js
16 ms
xaa6oyl.js
257 ms
vendor.css
28 ms
style.css
27 ms
vendor.global.min.js
48 ms
vendor.home.min.js
24 ms
main.home.min.js
26 ms
css
61 ms
story-platform.png
23 ms
embed
321 ms
coupons.png
17 ms
countrycrock.png
17 ms
sonos.png
18 ms
beechnut.png
17 ms
google.png
18 ms
PMA.png
26 ms
fx.png
26 ms
usa.png
27 ms
webbys.png
30 ms
trulia.png
31 ms
rci.png
30 ms
bd.png
30 ms
Arris.png
31 ms
suave.png
33 ms
lexus.png
35 ms
Popsicle.png
36 ms
epica.png
37 ms
Purdue.png
37 ms
kirk.jpg
302 ms
simon.jpg
300 ms
jacqueline.jpg
300 ms
heidi.jpg
301 ms
nicole.jpg
308 ms
phoebe.jpg
307 ms
richard.jpg
303 ms
stephen.jpg
301 ms
close.png
301 ms
www.storyworldwide.com
309 ms
logo-story.png
241 ms
header-BNhome.jpg
248 ms
bg-elipse.png
241 ms
bg-pioneering.jpg
242 ms
bg-yellow-stripe.png
242 ms
bg-grey-stripe.png
242 ms
bg-our-people-stripe.png
243 ms
ico-twitter.png
244 ms
ico-linkedin.png
244 ms
analytics.js
196 ms
js
107 ms
init_embed.js
146 ms
collect
23 ms
-NkoGegKUR1RwPJqZfgyxbYsP7INGJX8d99KSl4EYIqffO5FgsMdeMJ6Mk6g5Msfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
73 ms
y7lebkjgREBJK96VQi37ZiwlidHJgAgmTjOEEzwu1L8.ttf
115 ms
dazS1PrQQuCxC3iOAJFEJd6Naowg1QhaIq8kLGtQSos.ttf
144 ms
MEz38VLIFL-t46JUtkIEgD07foQZrO1EElZKDKPS5Eo.ttf
253 ms
dazS1PrQQuCxC3iOAJFEJTdGNerWpg2Hn6A-BxWgZ_I.ttf
255 ms
icomoon.ttf
23 ms
slick.woff
32 ms
jk8mTFw-vODKWnTFtBLlhGNrOjSKd-DnqeJYgllVs3jff4rfggMdeMJ6Mk6g5Mofb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
114 ms
ZCYqc7Zu0AQJTxfWLwcJlvQDoc9WUd4GqPfCAMO1Y3CffHefggMdeMJ6Mk6g5gBfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
175 ms
2BzIgnO8g6_ePgLaYixybTPl4j0KC9QA1urhXGY3m_jffJhRgsMdeMJ6Mk6g5Msfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
252 ms
F8FUemwfWh4zDdQbwPfrOgcAwZriNxJyxxfDqwHhjovffwQHggMdeMJ6Mk6g5Mifb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
253 ms
common.js
108 ms
map.js
109 ms
google4.png
63 ms
overlay.js
62 ms
util.js
92 ms
onion.js
90 ms
search_impl.js
91 ms
p.gif
189 ms
stats.js
41 ms
openhand_8_8.cur
31 ms
ViewportInfoService.GetViewportInfo
42 ms
transparent.png
31 ms
controls.js
24 ms
ViewportInfoService.GetViewportInfo
43 ms
storyworldwide.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Names and labels
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.
Impact
Issue
Image elements do not have [alt] attributes
storyworldwide.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
storyworldwide.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Storyworldwide.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 Storyworldwide.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.
storyworldwide.com
Open Graph description is not detected on the main page of Story Worldwide. 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: