Access historiang.com. Historia National Geographic. Antiguo Egipto, Grecia Clásica, Antigua Roma, Edad Media, Segunda Guer...

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value5.7 s

17/100

25%

SI (Speed Index)

Value9.0 s

14/100

10%

TBT (Total Blocking Time)

Value1,730 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.044

99/100

15%

TTI (Time to Interactive)

Value20.7 s

2/100

10%

historiang.com

341 ms

historia

328 ms

bootstrap.css

525 ms

fonts.css

314 ms

jquery-ui.css

328 ms

Our browser made a total of 123 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Historiang.com, 38% (47 requests) were made to Nationalgeographic.com.es and 11% (14 requests) were made to Secure.flashtalking.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Nationalgeographic.com.es.

Content Size

3.7 MB

After Optimization

2.3 MB

In fact, the total size of Historiang.com main page is 3.7 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. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 61.9 kB

Original 81.5 kB
After minification 79.6 kB
After compression 19.5 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 61.9 kB or 76% of the original size.

Image Optimization

-2%

Potential reduce by 38.6 kB

Original 1.8 MB
After minification 1.7 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. Historia Ng images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 1.0 MB

Original 1.5 MB
After minification 1.5 MB
After compression 478.9 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.0 MB or 68% of the original size.

CSS Optimization

-87%

Potential reduce by 343.8 kB

Original 395.2 kB
After minification 287.4 kB
After compression 51.4 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. Historiang.com needs all CSS files to be minified and compressed as it can save up to 343.8 kB or 87% of the original size.

Requests Now

108

After Optimization

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

Accessibility Issues

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.

High

[aria-*] attributes do not match their roles

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes do not have valid values

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

High

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

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

ES
Language Claimed

ES
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Historiang.com 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 Historiang.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

historiang.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Historia National Geographic. Antiguo Egipto, Grecia Clásica, Antigua Roma, Edad Media, Segunda Guerra Mundial, personajes históricos…

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

historiang.com

historia

bootstrap.css

fonts.css

jquery-ui.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

historiang.com

historia

bootstrap.css

fonts.css

jquery-ui.css

magnific-popup.css

general.css

modules.css

modernizr.js

jwplayer.js

rbaplayer.js

cache.mgr.js

gpt.js

pubads_impl_82.js

container.html

hotjar-108988.js

b90d3e81portada_ng_383_200x265.jpg

0c51a139portada_viajes_192_200x265.jpg

8a8b226cportada_historia_147_200x265.jpg

ng_logo.svg

tutankhamon_960x482_d11cf031.JPG

viva-la-pepa_960x482_48d37811.jpg

oman1_960x482_b9cd3372.JPG

sejmet2_960x482_5b0de752.JPG

moneda1_720x488_cd2a25c0.JPG

tumbaetrusca1_720x488_f3ebc32e.JPG

tutankhamon_400x400_c52216d0.JPG

cesar_400x400_a7569b8e.JPG

138-hatshepsut-1_400x400_61c1a517.jpg

julio-cesar_400x400_00c690a5.JPG

el-triunfo-de-la-muerte-detalle_400x400_f5bb04db.jpg

sejmet2_400x400_82941c9c.JPG

oman7_400x400_2fcbe64a.JPG

album-orz023761-1_400x400_284fd8a8.jpg

osiris6_720x488_b6e7fbaf.JPG

moneda_720x488_19b0e328.JPG

bg_personajes.jpg

ng_historia_bg.jpg

artemochica4_720x488_79cd7b61.JPG

tortugas1_720x488_f0183728.JPG

meroe1_720x488_c96d6887.JPG

abrigodejusto3_720x488_1caf581c.JPG

lattara1_720x488_11dc0c6d.JPG