Tools & Wizards About Us
weylin.com screenshot

Report Summary

  • 56

    Performance

    Renders faster than
    72% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 96

    SEO

    Google-friendlier than
    90% of websites

weylin.com

Williamsburg's Most Exceptional Event Space | WEYLIN

Page Load Speed

908 ms in total

First Response

110 ms

Resources Loaded

738 ms

Page Rendered

60 ms

weylin.com screenshot

About Website

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

Formerly the Williamsburgh Savings Bank, Weylin captures the history and elegance of New York City now as a meticulously restored extraordinary event space.

Visit weylin.com

Key Findings

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

weylin.com performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

51/100

10%

LCP (Largest Contentful Paint)

Value5.9 s

14/100

25%

SI (Speed Index)

Value4.1 s

79/100

10%

TBT (Total Blocking Time)

Value440 ms

64/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.0 s

52/100

10%

Network Requests Diagram

weylin.com

110 ms

weylin.com

222 ms

analytics.js

45 ms

wp-emoji-release.min.js

29 ms

bootstrap.css

33 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 61% of them (36 requests) were addressed to the original Weylin.com, 15% (9 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (233 ms) belongs to the original domain Weylin.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 29.7 kB (12%)

Content Size

256.0 kB

After Optimization

226.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-76%

Potential reduce by 18.3 kB

  • Original 24.0 kB
  • After minification 21.9 kB
  • After compression 5.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 18.3 kB or 76% of the original size.

Image Optimization

-25%

Potential reduce by 3.1 kB

  • Original 12.4 kB
  • After minification 9.3 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, WEYLIN needs image optimization as it can save up to 3.1 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-2%

Potential reduce by 3.2 kB

  • Original 151.2 kB
  • After minification 151.2 kB
  • After compression 148.0 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. This website has mostly compressed JavaScripts.

CSS Optimization

-7%

Potential reduce by 5.1 kB

  • Original 68.3 kB
  • After minification 68.3 kB
  • After compression 63.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. Weylin.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 36 (77%)

Requests Now

47

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

weylin.com

weylin.com

110 ms

weylin.com

weylin.com

222 ms

analytics.js

analytics.js

45 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

29 ms

bootstrap.css

bootstrap.css

33 ms

shortcodes.css

shortcodes.css

30 ms

chosen.css

chosen.css

31 ms

client.css

client.css

31 ms

font-awesome.min.css

font-awesome.min.css

51 ms

bootstrap.css

bootstrap.css

37 ms

jquery.fancybox.css

jquery.fancybox.css

43 ms

jquery.mCustomScrollbar.css

jquery.mCustomScrollbar.css

44 ms

meanmenu.min.css

meanmenu.min.css

44 ms

slick.css

slick.css

45 ms

theme.min.css

theme.min.css

48 ms

custom.css

custom.css

52 ms

jquery.js

jquery.js

55 ms

jquery-migrate.min.js

jquery-migrate.min.js

56 ms

bootstrap.js

bootstrap.js

56 ms

init.js

init.js

55 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

59 ms

jquery.mCustomScrollbar.concat.min.js

jquery.mCustomScrollbar.concat.min.js

59 ms

jquery.meanmenu.js

jquery.meanmenu.js

63 ms

slick.js

slick.js

62 ms

script.js

script.js

59 ms

email-decode.min.js

email-decode.min.js

56 ms

icheck.min.js

icheck.min.js

69 ms

chosen.jquery.js

chosen.jquery.js

71 ms

jpibfi.client.js

jpibfi.client.js

73 ms

ssba.js

ssba.js

71 ms

wp-embed.min.js

wp-embed.min.js

70 ms

conversion.js

conversion.js

55 ms

59631.js

59631.js

135 ms

collect

collect

20 ms

js

js

90 ms

css

css

36 ms

css

css

48 ms

gtm.js

gtm.js

75 ms

collect

collect

53 ms

fbevents.js

fbevents.js

73 ms

weylin-logo-brown.png

weylin-logo-brown.png

71 ms

100 ms

mail.png

mail.png

233 ms

facebook-light.png

facebook-light.png

64 ms

twitter-light.png

twitter-light.png

63 ms

pinterest-light.png

pinterest-light.png

62 ms

instagram-light2.png

instagram-light2.png

62 ms

update.min.js

update.min.js

74 ms

sf-ui-text-light-webfont.woff

sf-ui-text-light-webfont.woff

211 ms

mtGh4-RGJqfMvt7P8FUr0Q1j-Hf1Bkll8g.ttf

mtGh4-RGJqfMvt7P8FUr0Q1j-Hf1Bkll8g.ttf

52 ms

mtGm4-RGJqfMvt7P8FUr0Q1j-Hf1DrpG4iNhNQ.ttf

mtGm4-RGJqfMvt7P8FUr0Q1j-Hf1DrpG4iNhNQ.ttf

57 ms

mtGm4-RGJqfMvt7P8FUr0Q1j-Hf1DuJH4iNhNQ.ttf

mtGm4-RGJqfMvt7P8FUr0Q1j-Hf1DuJH4iNhNQ.ttf

61 ms

mtGm4-RGJqfMvt7P8FUr0Q1j-Hf1DvJA4iNhNQ.ttf

mtGm4-RGJqfMvt7P8FUr0Q1j-Hf1DvJA4iNhNQ.ttf

65 ms

Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_GbQbMZhKg.ttf

Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_GbQbMZhKg.ttf

66 ms

Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_DjRbMZhKg.ttf

Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_DjRbMZhKg.ttf

65 ms

Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_DjQbMZhKg.ttf

Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_DjQbMZhKg.ttf

67 ms

Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_ObXbMZhKg.ttf

Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_ObXbMZhKg.ttf

67 ms

Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_N_XbMZhKg.ttf

Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_N_XbMZhKg.ttf

64 ms

31 ms

Accessibility Review

weylin.com accessibility score

97

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

Links do not have a discernible name

Best Practices

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

weylin.com SEO score

96

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

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

weylin.com

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