Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 60

    SEO

    Google-friendlier than
    23% of websites

sego.es

SEGO | Sociedad Española de Ginecología y Obstetricia

Page Load Speed

3.3 sec in total

First Response

310 ms

Resources Loaded

2.8 sec

Page Rendered

231 ms

sego.es screenshot

About Website

Click here to check amazing SEGO content for Spain. Otherwise, check out these important facts you probably never knew about sego.es

SEGO Sociedad Española de Ginecología y Obstetricia

Visit sego.es

Key Findings

We analyzed Sego.es page load time and found that the first response time was 310 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

sego.es performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value12.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value15.4 s

0/100

25%

SI (Speed Index)

Value13.2 s

2/100

10%

TBT (Total Blocking Time)

Value160 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0.011

100/100

15%

TTI (Time to Interactive)

Value19.3 s

2/100

10%

Network Requests Diagram

sego.es

310 ms

sego.es

708 ms

jquery-ui.css

316 ms

jquery-ui.theme.css

419 ms

bootstrap-theme.min.css

60 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 82% of them (46 requests) were addressed to the original Sego.es, 7% (4 requests) were made to Use.fontawesome.com and 4% (2 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (979 ms) belongs to the original domain Sego.es.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.0 MB (45%)

Content Size

6.6 MB

After Optimization

3.6 MB

In fact, the total size of Sego.es main page is 6.6 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. 40% of websites need less resources to load. Images take 4.7 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 42.2 kB

  • Original 53.2 kB
  • After minification 47.9 kB
  • After compression 11.1 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 42.2 kB or 79% of the original size.

Image Optimization

-32%

Potential reduce by 1.5 MB

  • Original 4.7 MB
  • After minification 3.2 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, SEGO needs image optimization as it can save up to 1.5 MB or 32% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-75%

Potential reduce by 1.1 MB

  • Original 1.5 MB
  • After minification 1.2 MB
  • After compression 379.2 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 1.1 MB or 75% of the original size.

CSS Optimization

-82%

Potential reduce by 254.4 kB

  • Original 309.5 kB
  • After minification 276.0 kB
  • After compression 55.1 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. Sego.es needs all CSS files to be minified and compressed as it can save up to 254.4 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (38%)

Requests Now

53

After Optimization

33

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

Accessibility Review

sego.es accessibility score

86

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA input fields do not have accessible names

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.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

sego.es best practices score

58

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

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

sego.es SEO score

60

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

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

High

robots.txt is not valid

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    ES

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sego.es can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Sego.es main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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