Tools & Wizards About Us
mobile.fishbowl.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

mobile.fishbowl.com

Personica SSO - Login

Page Load Speed

1.2 sec in total

First Response

249 ms

Resources Loaded

796 ms

Page Rendered

152 ms

mobile.fishbowl.com screenshot

About Website

Welcome to mobile.fishbowl.com homepage info - get ready to check Mobile Fishbowl best content for United States right away, or after learning these important things about mobile.fishbowl.com

Visit mobile.fishbowl.com

Key Findings

We analyzed Mobile.fishbowl.com page load time and found that the first response time was 249 ms and then it took 948 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

mobile.fishbowl.com performance score

0

Network Requests Diagram

mobile.fishbowl.com

249 ms

login

168 ms

login

63 ms

login.fishbowl.com

45 ms

Login.aspx

30 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Mobile.fishbowl.com, 84% (21 requests) were made to Login.fishbowl.com and 8% (2 requests) were made to Auth.vibescm.com. The less responsive or slowest element that took the longest time to load (249 ms) belongs to the original domain Mobile.fishbowl.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 514.6 kB (72%)

Content Size

717.3 kB

After Optimization

202.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mobile.fishbowl.com main page is 717.3 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. 30% of websites need less resources to load. Javascripts take 572.8 kB which makes up the majority of the site volume.

HTML Optimization

-66%

Potential reduce by 11.6 kB

  • Original 17.5 kB
  • After minification 16.6 kB
  • After compression 5.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 11.6 kB or 66% of the original size.

Image Optimization

-7%

Potential reduce by 2.8 kB

  • Original 37.7 kB
  • After minification 34.9 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. Mobile Fishbowl images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 425.1 kB

  • Original 572.8 kB
  • After minification 546.7 kB
  • After compression 147.7 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 425.1 kB or 74% of the original size.

CSS Optimization

-84%

Potential reduce by 75.1 kB

  • Original 89.3 kB
  • After minification 69.3 kB
  • After compression 14.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. Mobile.fishbowl.com needs all CSS files to be minified and compressed as it can save up to 75.1 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (60%)

Requests Now

20

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mobile.fishbowl.com

mobile.fishbowl.com

249 ms

login

login

168 ms

login

login

63 ms

login.fishbowl.com

login.fishbowl.com

45 ms

Login.aspx

Login.aspx

30 ms

Master.css

Master.css

17 ms

jquery-1.4.js

jquery-1.4.js

30 ms

jquery-ui.min.js

jquery-ui.min.js

83 ms

modal.css

modal.css

77 ms

framework.css

framework.css

43 ms

WebResource.axd

WebResource.axd

26 ms

WebResource.axd

WebResource.axd

65 ms

WebResource.axd

WebResource.axd

40 ms

ScriptResource.axd

ScriptResource.axd

62 ms

Telerik.Web.UI.WebResource.axd

Telerik.Web.UI.WebResource.axd

138 ms

WebResource.axd

WebResource.axd

41 ms

Framework.js

Framework.js

43 ms

ApplicationCommon.js

ApplicationCommon.js

53 ms

ExceptionHandling.js

ExceptionHandling.js

62 ms

headerGradient.png

headerGradient.png

6 ms

blank.gif

blank.gif

7 ms

loginLogo.png

loginLogo.png

30 ms

gradientSprite.png

gradientSprite.png

28 ms

iconSprite.png

iconSprite.png

13 ms

buttonGradientSprite.png

buttonGradientSprite.png

6 ms

SEO Factors

mobile.fishbowl.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mobile.fishbowl.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 Mobile.fishbowl.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.

Social Sharing Optimization

mobile.fishbowl.com

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