Tools & Wizards About Us
searchhub.org screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

searchhub.org

Lucidworks Search Hub

Page Load Speed

4.5 sec in total

First Response

39 ms

Resources Loaded

3.2 sec

Page Rendered

1.3 sec

searchhub.org screenshot

About Website

Click here to check amazing Search Hub content for United States. Otherwise, check out these important facts you probably never knew about searchhub.org

Lucidworks Fusion is the search and analytics platform powering the next generation of big data applications. SearchHub is an example application built on Fusion

Visit searchhub.org

Key Findings

We analyzed Searchhub.org page load time and found that the first response time was 39 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

searchhub.org performance score

0

Network Requests Diagram

searchhub.org

39 ms

1128 ms

css

72 ms

font-awesome.min.css

45 ms

foundation.css

152 ms

Our browser made a total of 104 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Searchhub.org, 77% (80 requests) were made to Lucidworks.com and 3% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Lucidworks.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.5 MB (39%)

Content Size

8.9 MB

After Optimization

5.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Searchhub.org main page is 8.9 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 7.5 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 48.6 kB

  • Original 60.0 kB
  • After minification 54.2 kB
  • After compression 11.4 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 48.6 kB or 81% of the original size.

Image Optimization

-33%

Potential reduce by 2.5 MB

  • Original 7.5 MB
  • After minification 5.1 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. Obviously, Search Hub needs image optimization as it can save up to 2.5 MB or 33% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-70%

Potential reduce by 683.3 kB

  • Original 971.2 kB
  • After minification 882.9 kB
  • After compression 287.8 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 683.3 kB or 70% of the original size.

CSS Optimization

-86%

Potential reduce by 286.8 kB

  • Original 333.8 kB
  • After minification 274.3 kB
  • After compression 47.0 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. Searchhub.org needs all CSS files to be minified and compressed as it can save up to 286.8 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 69 (72%)

Requests Now

96

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

searchhub.org

searchhub.org

39 ms

1128 ms

css

css

72 ms

font-awesome.min.css

font-awesome.min.css

45 ms

foundation.css

foundation.css

152 ms

modernizr.js

modernizr.js

207 ms

jquery.js

jquery.js

289 ms

foundation.min.js

foundation.min.js

309 ms

global.css

global.css

240 ms

effects.css

effects.css

242 ms

animations.css

animations.css

240 ms

header.css

header.css

273 ms

footer.css

footer.css

320 ms

elements.css

elements.css

319 ms

icons.css

icons.css

320 ms

home.css

home.css

339 ms

blog.css

blog.css

348 ms

labs.css

labs.css

350 ms

sections.css

sections.css

367 ms

section-hero.css

section-hero.css

369 ms

section-showcase.css

section-showcase.css

369 ms

section-slider.css

section-slider.css

399 ms

section-toast.css

section-toast.css

411 ms

themes.css

themes.css

416 ms

content-integrations.css

content-integrations.css

433 ms

content-logo-bar.css

content-logo-bar.css

434 ms

content-diagram-fusion.css

content-diagram-fusion.css

435 ms

content-lr-register.css

content-lr-register.css

467 ms

content-support-form.css

content-support-form.css

476 ms

content-toast-download-fusion.css

content-toast-download-fusion.css

483 ms

content-icon-list.css

content-icon-list.css

500 ms

content-quote.css

content-quote.css

501 ms

content-partners-list.css

content-partners-list.css

503 ms

page-fusion.css

page-fusion.css

532 ms

page-silk.css

page-silk.css

544 ms

page-solr-support.css

page-solr-support.css

552 ms

page-company.css

page-company.css

569 ms

page-videos.css

page-videos.css

573 ms

page-customers.css

page-customers.css

571 ms

swiper.min.css

swiper.min.css

38 ms

swiper.min.js

swiper.min.js

62 ms

2247070035.js

2247070035.js

602 ms

magnific-popup.css

magnific-popup.css

597 ms

style.css

style.css

467 ms

prettyPhoto.css

prettyPhoto.css

420 ms

wp-video-lightbox.css

wp-video-lightbox.css

419 ms

swiper-shim.js

swiper-shim.js

420 ms

nav.js

nav.js

421 ms

parallax.js

parallax.js

415 ms

section-showcase.js

section-showcase.js

396 ms

section-slider.js

section-slider.js

391 ms

section-toast.js

section-toast.js

406 ms

multistep-form.js

multistep-form.js

407 ms

main.js

main.js

408 ms

blog.js

blog.js

414 ms

isotope.pkgd.min.js

isotope.pkgd.min.js

413 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

419 ms

jquery.infinitescroll.min.js

jquery.infinitescroll.min.js

421 ms

imagesloaded.pkgd.min.js

imagesloaded.pkgd.min.js

421 ms

jquery.js

jquery.js

488 ms

jquery-migrate.min.js

jquery-migrate.min.js

415 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

416 ms

video-lightbox.js

video-lightbox.js

418 ms

svg-inline-min.js

svg-inline-min.js

420 ms

ssba.min.js

ssba.min.js

419 ms

wp-embed.min.js

wp-embed.min.js

487 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

132 ms

event

event

325 ms

1EqTbJWOZQBfhZ0e3RL9uvesZW2xOQ-xsNqO47m55DA.ttf

1EqTbJWOZQBfhZ0e3RL9uvesZW2xOQ-xsNqO47m55DA.ttf

326 ms

0DeoTBMnW4sOpD0Zb8OQSALUuEpTyoUstqEm5AMlJo4.ttf

0DeoTBMnW4sOpD0Zb8OQSALUuEpTyoUstqEm5AMlJo4.ttf

357 ms

MZ1aViPqjfvZwVD_tzjjkwLUuEpTyoUstqEm5AMlJo4.ttf

MZ1aViPqjfvZwVD_tzjjkwLUuEpTyoUstqEm5AMlJo4.ttf

357 ms

munchkin-beta.js

munchkin-beta.js

340 ms

fbevents.js

fbevents.js

529 ms

bat.js

bat.js

542 ms

lucidworks-white.svg

lucidworks-white.svg

310 ms

phone.png

phone.png

311 ms

google-search-appliance-replacement.png

google-search-appliance-replacement.png

563 ms

understanding-transaction-logs-softcommit-and-commit.jpg

understanding-transaction-logs-softcommit-and-commit.jpg

496 ms

faceted-search-apache-solr1.png

faceted-search-apache-solr1.png

563 ms

nested-queries-solr1.png

nested-queries-solr1.png

999 ms

fusion_access_users.jpg

fusion_access_users.jpg

656 ms

solr-developer-survey-2015-thumb.gif

solr-developer-survey-2015-thumb.gif

524 ms

fusion-ssl.jpg

fusion-ssl.jpg

633 ms

Lucidworks_Dark-Data__Pitch-1.png

Lucidworks_Dark-Data__Pitch-1.png

1106 ms

solr-daterangefield.png

solr-daterangefield.png

708 ms

trey-grainger.png

trey-grainger.png

779 ms

query-solr-config.jpg

query-solr-config.jpg

989 ms

apache-solr-history.png

apache-solr-history.png

798 ms

q_for_quickstart.png

q_for_quickstart.png

846 ms

lucid-works-white.svg

lucid-works-white.svg

847 ms

7335.js

7335.js

354 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

282 ms

analytics.js

analytics.js

312 ms

fusion-background.png

fusion-background.png

652 ms

silk-background.png

silk-background.png

706 ms

solr-support-background.png

solr-support-background.png

705 ms

munchkin.js

munchkin.js

24 ms

visitWebPage

visitWebPage

389 ms

collect

collect

24 ms

s

s

26 ms

u

u

27 ms

collect

collect

61 ms

ga-audiences

ga-audiences

62 ms

98 ms

SEO Factors

searchhub.org 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 Searchhub.org 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 Searchhub.org 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

searchhub.org

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