Report Summary

  • 98

    Performance

    Renders faster than
    95% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

sourcesfinding.com

Finding Sources

Page Load Speed

1.3 sec in total

First Response

166 ms

Resources Loaded

1.1 sec

Page Rendered

122 ms

sourcesfinding.com screenshot

About Website

Click here to check amazing Sources Finding content. Otherwise, check out these important facts you probably never knew about sourcesfinding.com

Research, American History, presidents, primary sources, 11th grade social studies, finding sources

Visit sourcesfinding.com

Key Findings

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

Performance Metrics

sourcesfinding.com performance score

98

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.0 s

100/100

10%

LCP (Largest Contentful Paint)

Value2.4 s

91/100

25%

SI (Speed Index)

Value1.0 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.036

100/100

15%

TTI (Time to Interactive)

Value1.0 s

100/100

10%

Network Requests Diagram

sourcesfinding.com

166 ms

spacer.gif

39 ms

design_0081_3.jpg

41 ms

design_0081_4.jpg

73 ms

increment_page_counter.jsp

868 ms

Our browser made a total of 18 requests to load all elements on the main page. We found that 22% of them (4 requests) were addressed to the original Sourcesfinding.com, 72% (13 requests) were made to Webhosting.web.com and 6% (1 request) were made to Svcs.myregisteredsite.com. The less responsive or slowest element that took the longest time to load (868 ms) relates to the external source Svcs.myregisteredsite.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 25.3 kB (8%)

Content Size

314.1 kB

After Optimization

288.7 kB

In fact, the total size of Sourcesfinding.com main page is 314.1 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 294.0 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 15.8 kB

  • Original 20.1 kB
  • After minification 16.7 kB
  • After compression 4.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 3.3 kB, which is 17% 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 15.8 kB or 79% of the original size.

Image Optimization

-3%

Potential reduce by 9.6 kB

  • Original 294.0 kB
  • After minification 284.4 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. Sources Finding images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 7 (41%)

Requests Now

17

After Optimization

10

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

Accessibility Review

sourcesfinding.com accessibility score

72

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

Best Practices

sourcesfinding.com best practices score

75

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

SEO Factors

sourcesfinding.com SEO score

67

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 Sourcesfinding.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 Sourcesfinding.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 Sources Finding. 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: