Tools & Wizards About Us
trusearch.com screenshot

Report Summary

  • 83

    Performance

    Renders faster than
    88% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

trusearch.com

TruSearch.com

Page Load Speed

739 ms in total

First Response

126 ms

Resources Loaded

503 ms

Page Rendered

110 ms

trusearch.com screenshot

About Website

Welcome to trusearch.com homepage info - get ready to check Tru Search best content for United States right away, or after learning these important things about trusearch.com

TruSearch.com

Visit trusearch.com

Key Findings

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

Performance Metrics

trusearch.com performance score

83

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

63/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

62/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.025

100/100

15%

TTI (Time to Interactive)

Value6.0 s

65/100

10%

Network Requests Diagram

trusearch.com

126 ms

jquery131.js

138 ms

home.css

70 ms

geosel.js

71 ms

tabs.css

70 ms

Our browser made a total of 16 requests to load all elements on the main page. We found that 88% of them (14 requests) were addressed to the original Trusearch.com, 13% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (138 ms) belongs to the original domain Trusearch.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 75.1 kB (62%)

Content Size

120.2 kB

After Optimization

45.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Trusearch.com main page is 120.2 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. Javascripts take 110.5 kB which makes up the majority of the site volume.

HTML Optimization

-63%

Potential reduce by 3.0 kB

  • Original 4.7 kB
  • After minification 4.5 kB
  • After compression 1.7 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 3.0 kB or 63% of the original size.

Image Optimization

-0%

Potential reduce by 2 B

  • Original 1.8 kB
  • After minification 1.8 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. Tru Search images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 70.1 kB

  • Original 110.5 kB
  • After minification 109.3 kB
  • After compression 40.4 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 70.1 kB or 63% of the original size.

CSS Optimization

-62%

Potential reduce by 2.1 kB

  • Original 3.3 kB
  • After minification 2.9 kB
  • After compression 1.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. Trusearch.com needs all CSS files to be minified and compressed as it can save up to 2.1 kB or 62% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (40%)

Requests Now

15

After Optimization

9

  • Images
  • JavaScript
  • CSS

The browser has sent 15 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tru Search. 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.

Network Requests Diagram

trusearch.com

trusearch.com

126 ms

jquery131.js

jquery131.js

138 ms

home.css

home.css

70 ms

geosel.js

geosel.js

71 ms

tabs.css

tabs.css

70 ms

geosel.css

geosel.css

72 ms

analytics.js

analytics.js

21 ms

logo.png

logo.png

70 ms

homebg.gif

homebg.gif

71 ms

search_small.gif

search_small.gif

71 ms

tabbg.gif

tabbg.gif

72 ms

tableft.gif

tableft.gif

72 ms

tabright.gif

tabright.gif

73 ms

menuleft.gif

menuleft.gif

137 ms

menuright.gif

menuright.gif

138 ms

collect

collect

24 ms

Accessibility Review

trusearch.com accessibility score

66

Accessibility Issues

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

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Form elements do not have associated labels

High

<object> elements do not have alternate text

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Best Practices

trusearch.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

trusearch.com SEO score

90

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

High

Tap targets are not sized appropriately

Content Best Practices

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

Impact

Issue

High

Document uses plugins

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    WINDOWS-1251

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Trusearch.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 Trusearch.com main page’s claimed encoding is windows-1251. 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

trusearch.com

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