Tools & Wizards About Us
yesnumber.pt screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

yesnumber.pt

Home-EN - Yesnumber

Page Load Speed

11.8 sec in total

First Response

3.4 sec

Resources Loaded

7.2 sec

Page Rendered

1.1 sec

yesnumber.pt screenshot

About Website

Visit yesnumber.pt now to see the best up-to-date Yesnumber content and also check out these interesting facts you probably never knew about yesnumber.pt

WE ARE YES!

Visit yesnumber.pt

Key Findings

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

Performance Metrics

yesnumber.pt performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value14.2 s

0/100

25%

SI (Speed Index)

Value12.6 s

3/100

10%

TBT (Total Blocking Time)

Value280 ms

81/100

30%

CLS (Cumulative Layout Shift)

Value0.053

98/100

15%

TTI (Time to Interactive)

Value11.7 s

17/100

10%

Network Requests Diagram

3418 ms

css

27 ms

chaty-front.min.css

194 ms

styles.css

289 ms

grid.min.css

296 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 74% of them (62 requests) were addressed to the original Yesnumber.pt, 23% (19 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Yesnumber.pt.

Page Optimization Overview & Recommendations

Page size can be reduced by 922.5 kB (16%)

Content Size

5.8 MB

After Optimization

4.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yesnumber.pt main page is 5.8 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. 65% of websites need less resources to load. Images take 5.3 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 169.6 kB

  • Original 199.5 kB
  • After minification 197.0 kB
  • After compression 30.0 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 169.6 kB or 85% of the original size.

Image Optimization

-13%

Potential reduce by 661.2 kB

  • Original 5.3 MB
  • After minification 4.6 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, Yesnumber needs image optimization as it can save up to 661.2 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

-9%

Potential reduce by 21.1 kB

  • Original 227.5 kB
  • After minification 227.5 kB
  • After compression 206.4 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

-45%

Potential reduce by 70.6 kB

  • Original 155.3 kB
  • After minification 155.3 kB
  • After compression 84.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. Yesnumber.pt needs all CSS files to be minified and compressed as it can save up to 70.6 kB or 45% of the original size.

Requests Breakdown

Number of requests can be reduced by 47 (75%)

Requests Now

63

After Optimization

16

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

3418 ms

css

css

27 ms

chaty-front.min.css

chaty-front.min.css

194 ms

styles.css

styles.css

289 ms

grid.min.css

grid.min.css

296 ms

helper-parts.min.css

helper-parts.min.css

294 ms

main.min.css

main.min.css

414 ms

style.min.css

style.min.css

298 ms

theme.min.css

theme.min.css

301 ms

header-footer.min.css

header-footer.min.css

390 ms

frontend.min.css

frontend.min.css

394 ms

custom-frontend-lite.min.css

custom-frontend-lite.min.css

406 ms

swiper.min.css

swiper.min.css

310 ms

custom-pro-frontend-lite.min.css

custom-pro-frontend-lite.min.css

317 ms

all.min.css

all.min.css

409 ms

v4-shims.min.css

v4-shims.min.css

405 ms

css

css

19 ms

jquery.min.js

jquery.min.js

512 ms

jquery-migrate.min.js

jquery-migrate.min.js

421 ms

v4-shims.min.js

v4-shims.min.js

421 ms

js

js

92 ms

custom-pro-widget-nav-menu.min.css

custom-pro-widget-nav-menu.min.css

422 ms

widget-posts.min.css

widget-posts.min.css

504 ms

animations.min.css

animations.min.css

506 ms

cht-front-script.min.js

cht-front-script.min.js

633 ms

index.js

index.js

633 ms

index.js

index.js

634 ms

core.min.js

core.min.js

634 ms

main.min.js

main.min.js

635 ms

hello-frontend.min.js

hello-frontend.min.js

635 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

636 ms

effect.min.js

effect.min.js

637 ms

jquery.twentytwenty.js

jquery.twentytwenty.js

635 ms

jquery.event.move.js

jquery.event.move.js

708 ms

typed.js

typed.js

710 ms

imagesloaded.min.js

imagesloaded.min.js

707 ms

webpack.runtime.min.js

webpack.runtime.min.js

738 ms

frontend-modules.min.js

frontend-modules.min.js

736 ms

waypoints.min.js

waypoints.min.js

738 ms

frontend.min.js

frontend.min.js

815 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

718 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

618 ms

wp-polyfill.min.js

wp-polyfill.min.js

658 ms

hooks.min.js

hooks.min.js

639 ms

i18n.min.js

i18n.min.js

645 ms

elementor.js

elementor.js

706 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

619 ms

frontend.min.js

frontend.min.js

618 ms

elements-handlers.min.js

elements-handlers.min.js

639 ms

jquery.sticky.min.js

jquery.sticky.min.js

631 ms

MicrosoftTeams-image-10-1024x1024.png

MicrosoftTeams-image-10-1024x1024.png

420 ms

pt.svg

pt.svg

2368 ms

MicrosoftTeams-image-9-e1674828126210-1024x560.png

MicrosoftTeams-image-9-e1674828126210-1024x560.png

556 ms

Inicio-e1675426473244.png

Inicio-e1675426473244.png

884 ms

petzen.png

petzen.png

1179 ms

Social-Media_Mockup-e1681469493598-1024x595.png

Social-Media_Mockup-e1681469493598-1024x595.png

926 ms

Azeite-Olis-6.jpg

Azeite-Olis-6.jpg

601 ms

Mockup_petzen2-1024x768.png

Mockup_petzen2-1024x768.png

1050 ms

Ecommerce-e1683715250650-768x552.png

Ecommerce-e1683715250650-768x552.png

819 ms

Business-Cards-scaled-e1683717980103.jpg

Business-Cards-scaled-e1683717980103.jpg

867 ms

sinonimousual-logo-yellow-e1683718144219.jpg

sinonimousual-logo-yellow-e1683718144219.jpg

924 ms

property-styles-responsive-design-1.jpg

property-styles-responsive-design-1.jpg

970 ms

cozmoda-website-presentation-1-scaled.jpg

cozmoda-website-presentation-1-scaled.jpg

1074 ms

Napkins-du-chef-4.jpg

Napkins-du-chef-4.jpg

1033 ms

cofinanciado-por-pt2020-branco.png

cofinanciado-por-pt2020-branco.png

1069 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

33 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

43 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

60 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

71 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

74 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

74 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

73 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

72 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

71 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf

73 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

97 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

99 ms

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-4I-FV0Uw.ttf

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-4I-FV0Uw.ttf

99 ms

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-h4-FV0Uw.ttf

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-h4-FV0Uw.ttf

97 ms

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-ro-FV0Uw.ttf

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-ro-FV0Uw.ttf

98 ms

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-2Y-FV0Uw.ttf

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-2Y-FV0Uw.ttf

96 ms

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-NYiFV0Uw.ttf

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-NYiFV0Uw.ttf

99 ms

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-B4iFV0Uw.ttf

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-B4iFV0Uw.ttf

99 ms

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-WYiFV0Uw.ttf

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-WYiFV0Uw.ttf

98 ms

Accessibility Review

yesnumber.pt accessibility score

98

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

yesnumber.pt 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

SEO Factors

yesnumber.pt SEO score

93

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

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 Yesnumber.pt 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 Yesnumber.pt 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

yesnumber.pt

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