Tools & Wizards About Us
websays.com screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

websays.com

Websays masters Social Intelligence

Page Load Speed

3.7 sec in total

First Response

288 ms

Resources Loaded

3 sec

Page Rendered

417 ms

websays.com screenshot

About Website

Welcome to websays.com homepage info - get ready to check Websays best content for Spain right away, or after learning these important things about websays.com

Websays masters Social Listening and Intelligence since 2010. With a powerful real-time analytics dashboard and a team of data analysts, you can rely on us for an accurate data gathering and reporting...

Visit websays.com

Key Findings

We analyzed Websays.com page load time and found that the first response time was 288 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

websays.com performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

80/100

10%

LCP (Largest Contentful Paint)

Value13.8 s

0/100

25%

SI (Speed Index)

Value10.7 s

7/100

10%

TBT (Total Blocking Time)

Value5,000 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.083

93/100

15%

TTI (Time to Interactive)

Value29.5 s

0/100

10%

Network Requests Diagram

websays.com

288 ms

social-listening-tool

115 ms

gtm.js

71 ms

bootstrap.min.css

104 ms

bootstrap-theme.min.css

200 ms

Our browser made a total of 115 requests to load all elements on the main page. We found that 64% of them (74 requests) were addressed to the original Websays.com, 7% (8 requests) were made to Youtube.com and 6% (7 requests) were made to Static.hsappstatic.net. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Websays.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 122.3 kB (10%)

Content Size

1.2 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Websays.com main page is 1.2 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 848.5 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 51.6 kB

  • Original 64.2 kB
  • After minification 61.1 kB
  • After compression 12.6 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 51.6 kB or 80% of the original size.

Image Optimization

-13%

Potential reduce by 21.1 kB

  • Original 157.3 kB
  • After minification 136.2 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, Websays needs image optimization as it can save up to 21.1 kB or 13% 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 17.9 kB

  • Original 848.5 kB
  • After minification 848.5 kB
  • After compression 830.6 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

-18%

Potential reduce by 31.6 kB

  • Original 173.3 kB
  • After minification 173.3 kB
  • After compression 141.7 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. Websays.com needs all CSS files to be minified and compressed as it can save up to 31.6 kB or 18% of the original size.

Requests Breakdown

Number of requests can be reduced by 59 (57%)

Requests Now

103

After Optimization

44

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

websays.com

websays.com

288 ms

social-listening-tool

social-listening-tool

115 ms

gtm.js

gtm.js

71 ms

bootstrap.min.css

bootstrap.min.css

104 ms

bootstrap-theme.min.css

bootstrap-theme.min.css

200 ms

fonts.css

fonts.css

274 ms

font-awesome.min.css

font-awesome.min.css

275 ms

cached.css

cached.css

278 ms

cached.css

cached.css

281 ms

MeetingsEmbedCode.js

MeetingsEmbedCode.js

36 ms

T1A697B6ZC05QY582GNN.js

T1A697B6ZC05QY582GNN.js

277 ms

page.js

page.js

35 ms

jquery.min.js

jquery.min.js

401 ms

jquery-migrate.min.js

jquery-migrate.min.js

292 ms

addtoany.min.js

addtoany.min.js

391 ms

Modernizr.js

Modernizr.js

391 ms

Loader.js

Loader.js

392 ms

webfontLoader.min.js

webfontLoader.min.js

392 ms

webfontConfig.js

webfontConfig.js

419 ms

bootstrap.min.js

bootstrap.min.js

471 ms

Menu.js

Menu.js

567 ms

jquery.scrollUp.js

jquery.scrollUp.js

469 ms

Pager.js

Pager.js

464 ms

Mailchimp.js

Mailchimp.js

598 ms

imagesLoaded.min.js

imagesLoaded.min.js

588 ms

imagesloaded.min.js

imagesloaded.min.js

598 ms

masonry.min.js

masonry.min.js

597 ms

Grid.js

Grid.js

587 ms

global.js

global.js

587 ms

style.min.css

style.min.css

696 ms

classic-themes.min.css

classic-themes.min.css

692 ms

form-basic.css

form-basic.css

695 ms

addtoany.min.css

addtoany.min.css

694 ms

slick.css

slick.css

692 ms

slick-theme.css

slick-theme.css

693 ms

slick.min.js

slick.min.js

1023 ms

global.js

global.js

1023 ms

analytics.js

analytics.js

65 ms

fscript.js

fscript.js

106 ms

header-background.svg

header-background.svg

751 ms

alerts_icon.png

alerts_icon.png

752 ms

clippings_icon.png

clippings_icon.png

752 ms

communities_icon.png

communities_icon.png

752 ms

comparisons_icon.png

comparisons_icon.png

754 ms

maps_icon.png

maps_icon.png

753 ms

reports_icon.png

reports_icon.png

755 ms

tech.svg

tech.svg

755 ms

data.svg

data.svg

762 ms

data2.svg

data2.svg

764 ms

ga.js

ga.js

81 ms

data3.svg

data3.svg

806 ms

iframe_api

iframe_api

107 ms

data4.svg

data4.svg

780 ms

anaid-hernandez

anaid-hernandez

115 ms

collect

collect

53 ms

sm.25.html

sm.25.html

34 ms

eso.BRQnzO8v.js

eso.BRQnzO8v.js

63 ms

__utm.gif

__utm.gif

43 ms

10884.otf

10884.otf

952 ms

10881.otf

10881.otf

957 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

910 ms

data5.svg

data5.svg

706 ms

collect

collect

159 ms

js

js

52 ms

data6.svg

data6.svg

891 ms

data7.svg

data7.svg

882 ms

www-widgetapi.js

www-widgetapi.js

14 ms

collect

collect

34 ms

Fn8Or13DnZo

Fn8Or13DnZo

156 ms

bundle.production.js

bundle.production.js

127 ms

book-info-early-requester.js

book-info-early-requester.js

123 ms

project_with_deps.css

project_with_deps.css

137 ms

configure-monitoring.js

configure-monitoring.js

145 ms

bundle.production.js

bundle.production.js

157 ms

project.js

project.js

203 ms

ga-audiences

ga-audiences

170 ms

people.svg

people.svg

841 ms

market.svg

market.svg

873 ms

tribe.svg

tribe.svg

764 ms

ga-audiences

ga-audiences

88 ms

trends.svg

trends.svg

769 ms

www-player.css

www-player.css

45 ms

www-embed-player.js

www-embed-player.js

78 ms

base.js

base.js

124 ms

bancsabadell.png

bancsabadell.png

752 ms

imagin-e1669740976153-150x150.png

imagin-e1669740976153-150x150.png

898 ms

bayer-logo-150x150.png

bayer-logo-150x150.png

887 ms

boehringer.jpg

boehringer.jpg

888 ms

theramex-vector-logo-small-150x150.png

theramex-vector-logo-small-150x150.png

887 ms

leo-pharma-e1662713991929.png

leo-pharma-e1662713991929.png

876 ms

10885.otf

10885.otf

892 ms

10882.otf

10882.otf

983 ms

fira.png

fira.png

803 ms

CLIENT-diputaci%C3%B3-150x150.jpg

CLIENT-diputaci%C3%B3-150x150.jpg

804 ms

accor.png

accor.png

834 ms

catalana.jpg

catalana.jpg

830 ms

ad_status.js

ad_status.js

229 ms

YjCNJ0mFj9HiCkQt39lQVpZzkP0G8dlYH-ABayRLdFs.js

YjCNJ0mFj9HiCkQt39lQVpZzkP0G8dlYH-ABayRLdFs.js

147 ms

embed.js

embed.js

94 ms

volotea.png

volotea.png

562 ms

rabat-150x150.png

rabat-150x150.png

562 ms

CLIENT-gobierno-per%C3%BA-150x150.png

CLIENT-gobierno-per%C3%BA-150x150.png

571 ms

populi.png

populi.png

572 ms

tinkle.png

tinkle.png

643 ms

zendesk.png

zendesk.png

652 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

204 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

208 ms

alert_close_loading.png

alert_close_loading.png

583 ms

id

id

70 ms

remote.js

remote.js

130 ms

sddefault.jpg

sddefault.jpg

154 ms

Create

Create

82 ms

GenerateIT

GenerateIT

13 ms

messenger.css

messenger.css

36 ms

messenger.js

messenger.js

58 ms

Accessibility Review

websays.com accessibility score

85

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

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

websays.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

websays.com SEO score

82

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

websays.com

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