Tools & Wizards About Us
goingout.com screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

goingout.com

Best Restaurant, Sports Bars, Lounges and Clubs in RI | GoingOut

Page Load Speed

774 ms in total

First Response

55 ms

Resources Loaded

646 ms

Page Rendered

73 ms

goingout.com screenshot

About Website

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

Find the Best Restaurant, Sports Bars, Lounge, Pubs, Nightclubs in Rhode Island. Book your event at top dining and nightlife venues on GoingOut!

Visit goingout.com

Key Findings

We analyzed Goingout.com page load time and found that the first response time was 55 ms and then it took 719 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

goingout.com performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value10.8 s

0/100

25%

SI (Speed Index)

Value5.4 s

56/100

10%

TBT (Total Blocking Time)

Value560 ms

52/100

30%

CLS (Cumulative Layout Shift)

Value0.452

20/100

15%

TTI (Time to Interactive)

Value9.1 s

33/100

10%

Network Requests Diagram

goingout.com

55 ms

patriotplace

121 ms

screen.css

13 ms

jquery-ui.css

39 ms

shared.css

23 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 71% of them (32 requests) were addressed to the original Goingout.com, 13% (6 requests) were made to Ssl.google-analytics.com and 7% (3 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (121 ms) belongs to the original domain Goingout.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 77.2 kB (18%)

Content Size

429.2 kB

After Optimization

352.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-75%

Potential reduce by 23.7 kB

  • Original 31.5 kB
  • After minification 29.7 kB
  • After compression 7.8 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 23.7 kB or 75% of the original size.

Image Optimization

-17%

Potential reduce by 22.7 kB

  • Original 135.2 kB
  • After minification 112.5 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. Obviously, Going Out needs image optimization as it can save up to 22.7 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-11%

Potential reduce by 26.0 kB

  • Original 232.8 kB
  • After minification 227.1 kB
  • After compression 206.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 26.0 kB or 11% of the original size.

CSS Optimization

-16%

Potential reduce by 4.7 kB

  • Original 29.7 kB
  • After minification 29.7 kB
  • After compression 25.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. Goingout.com needs all CSS files to be minified and compressed as it can save up to 4.7 kB or 16% of the original size.

Requests Breakdown

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

Requests Now

43

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

goingout.com

goingout.com

55 ms

patriotplace

patriotplace

121 ms

screen.css

screen.css

13 ms

jquery-ui.css

jquery-ui.css

39 ms

shared.css

shared.css

23 ms

prettyPhoto.css

prettyPhoto.css

31 ms

jquery.fancybox-1.3.4.css

jquery.fancybox-1.3.4.css

32 ms

main.css

main.css

35 ms

header.css

header.css

33 ms

search-results.css

search-results.css

33 ms

jquery.min.js

jquery.min.js

27 ms

jquery-ui.min.js

jquery-ui.min.js

32 ms

jquery.ba-bbq.js

jquery.ba-bbq.js

64 ms

lodash.compat.min.js

lodash.compat.min.js

66 ms

shared.js

shared.js

70 ms

jquery.fancybox-1.3.4.pack.js

jquery.fancybox-1.3.4.pack.js

72 ms

jquery.mousewheel-3.0.4.pack.js

jquery.mousewheel-3.0.4.pack.js

70 ms

jquery.easing-1.3.pack.js

jquery.easing-1.3.pack.js

71 ms

angular.min.js

angular.min.js

75 ms

main.js

main.js

74 ms

landingpage.js

landingpage.js

73 ms

tooltip.jquery.js

tooltip.jquery.js

73 ms

jquery.defaultvalue.js

jquery.defaultvalue.js

72 ms

jquery.dotdotdot.min.js

jquery.dotdotdot.min.js

72 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

91 ms

ga.js

ga.js

110 ms

fbevents.js

fbevents.js

67 ms

sdk.js

sdk.js

107 ms

78 ms

79 ms

75 ms

46 ms

GO-logo-2013.png

GO-logo-2013.png

45 ms

header-sprite.png

header-sprite.png

44 ms

circle-fb.png

circle-fb.png

71 ms

circle-gp.png

circle-gp.png

73 ms

img_sprite.png

img_sprite.png

77 ms

sdk.js

sdk.js

28 ms

__utm.gif

__utm.gif

40 ms

__utm.gif

__utm.gif

36 ms

__utm.gif

__utm.gif

42 ms

__utm.gif

__utm.gif

42 ms

__utm.gif

__utm.gif

41 ms

82 ms

print.css

print.css

15 ms

Accessibility Review

goingout.com accessibility score

73

Accessibility Issues

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.

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

goingout.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

goingout.com SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

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 Goingout.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 Goingout.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

goingout.com

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