Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 0

    Accessibility

  • 54

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 70

    SEO

    Google-friendlier than
    30% of websites

opinion.inquirer.net

Opinion Pieces From Our Top Editors On All Things Political | Inquirer.net

Page Load Speed

34.4 sec in total

First Response

2.2 sec

Resources Loaded

30.7 sec

Page Rendered

1.5 sec

opinion.inquirer.net screenshot

About Website

Visit opinion.inquirer.net now to see the best up-to-date Opinion Inquirer content for Philippines and also check out these interesting facts you probably never knew about opinion.inquirer.net

Opinion pieces from our top editors that start the discussion on all things political. Daily editorial cartoon.

Visit opinion.inquirer.net

Key Findings

We analyzed Opinion.inquirer.net page load time and found that the first response time was 2.2 sec and then it took 32.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

opinion.inquirer.net performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value8.9 s

1/100

25%

SI (Speed Index)

Value21.7 s

0/100

10%

TBT (Total Blocking Time)

Value3,370 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.269

46/100

15%

TTI (Time to Interactive)

Value42.8 s

0/100

10%

Network Requests Diagram

opinion.inquirer.net

2150 ms

css

103 ms

univ.css

467 ms

styleafter.css

435 ms

jquery.fancybox-1.3.7.min.css

461 ms

Our browser made a total of 500 requests to load all elements on the main page. We found that 7% of them (35 requests) were addressed to the original Opinion.inquirer.net, 8% (41 requests) were made to Inquirer.net and 4% (20 requests) were made to Us-u.openx.net. The less responsive or slowest element that took the longest time to load (19.9 sec) relates to the external source Pop.inquirer.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (28%)

Content Size

4.7 MB

After Optimization

3.4 MB

In fact, the total size of Opinion.inquirer.net main page is 4.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. 85% 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 3.1 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 127.1 kB

  • Original 163.2 kB
  • After minification 149.8 kB
  • After compression 36.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 127.1 kB or 78% of the original size.

Image Optimization

-8%

Potential reduce by 255.3 kB

  • Original 3.1 MB
  • After minification 2.9 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. Opinion Inquirer images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 846.0 kB

  • Original 1.3 MB
  • After minification 1.2 MB
  • After compression 442.5 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 846.0 kB or 66% of the original size.

CSS Optimization

-84%

Potential reduce by 61.4 kB

  • Original 72.8 kB
  • After minification 65.1 kB
  • After compression 11.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. Opinion.inquirer.net needs all CSS files to be minified and compressed as it can save up to 61.4 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 226 (53%)

Requests Now

423

After Optimization

197

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

Best Practices

opinion.inquirer.net best practices score

54

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

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

opinion.inquirer.net SEO score

70

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 uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Opinion.inquirer.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Opinion.inquirer.net 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

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