Report Summary

  • 75

    Performance

    Renders faster than
    84% of other websites

  • 57

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 58

    SEO

    Google-friendlier than
    20% of websites

thestoryoftheday.com

Cleveland Ohio Editorial Commercial Sports Photographer Photojournalist

Page Load Speed

1.1 sec in total

First Response

204 ms

Resources Loaded

359 ms

Page Rendered

532 ms

thestoryoftheday.com screenshot

About Website

Welcome to thestoryoftheday.com homepage info - get ready to check Thestoryoftheday best content right away, or after learning these important things about thestoryoftheday.com

Cleveland photographer Ken Blaze photographs people for magazines and corporate clients. The Ohio-based photojourmalist specializes in editorial, sports and documentary photography

Visit thestoryoftheday.com

Key Findings

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

Performance Metrics

thestoryoftheday.com performance score

75

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.8 s

100/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value1.0 s

100/100

10%

TBT (Total Blocking Time)

Value190 ms

90/100

30%

CLS (Cumulative Layout Shift)

Value0.026

100/100

15%

TTI (Time to Interactive)

Value1.2 s

100/100

10%

Network Requests Diagram

thestoryoftheday.com

204 ms

openerphoto1.jpg

113 ms

kenblazephotographer.jpg

76 ms

instagram2013.jpg

65 ms

twitter2013.jpg

47 ms

Our browser made a total of 7 requests to load all elements on the main page. We found that all of those requests were addressed to Thestoryoftheday.com and no external sources were called. The less responsive or slowest element that took the longest time to load (204 ms) belongs to the original domain Thestoryoftheday.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 24.4 kB (3%)

Content Size

966.5 kB

After Optimization

942.2 kB

In fact, the total size of Thestoryoftheday.com main page is 966.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only 10% of websites need less resources to load. Images take 959.5 kB which makes up the majority of the site volume.

HTML Optimization

-58%

Potential reduce by 4.1 kB

  • Original 7.0 kB
  • After minification 7.0 kB
  • After compression 2.9 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 4.1 kB or 58% of the original size.

Image Optimization

-2%

Potential reduce by 20.2 kB

  • Original 959.5 kB
  • After minification 939.2 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. Thestoryoftheday images are well optimized though.

Requests Breakdown

We found no issues to fix!

Requests Now

6

After Optimization

6

The browser has sent 6 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Thestoryoftheday. According to our analytics all requests are already optimized.

Accessibility Review

thestoryoftheday.com accessibility score

57

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

thestoryoftheday.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

thestoryoftheday.com SEO score

58

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Thestoryoftheday.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Thestoryoftheday.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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