Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 75% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

technology.inquirer.net

Inquirer Technology | Philippine News for Filipinos

Page Load Speed

24.7 sec in total

First Response

770 ms

Resources Loaded

22.6 sec

Page Rendered

1.3 sec

technology.inquirer.net screenshot

About Website

Welcome to technology.inquirer.net homepage info - get ready to check Technology Inquirer best content for Philippines right away, or after learning these important things about technology.inquirer.net

Philippine News for Filipinos

Visit technology.inquirer.net

Key Findings

We analyzed Technology.inquirer.net page load time and found that the first response time was 770 ms and then it took 23.9 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number 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

technology.inquirer.net performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value17.9 s

0/100

25%

SI (Speed Index)

Value18.3 s

0/100

10%

TBT (Total Blocking Time)

Value24,700 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.134

80/100

15%

TTI (Time to Interactive)

Value42.7 s

0/100

10%

Network Requests Diagram

technology.inquirer.net

770 ms

css

49 ms

univ980.css

523 ms

styleafter.css

520 ms

jquery.fancybox-1.3.7.min.css

517 ms

Our browser made a total of 542 requests to load all elements on the main page. We found that 12% of them (63 requests) were addressed to the original Technology.inquirer.net, 6% (34 requests) were made to Image2.pubmatic.com and 5% (29 requests) were made to Inquirer.net. The less responsive or slowest element that took the longest time to load (20 sec) relates to the external source Pop.inquirer.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (27%)

Content Size

5.2 MB

After Optimization

3.8 MB

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

HTML Optimization

-78%

Potential reduce by 131.5 kB

  • Original 167.9 kB
  • After minification 153.9 kB
  • After compression 36.4 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 131.5 kB or 78% of the original size.

Image Optimization

-6%

Potential reduce by 211.5 kB

  • Original 3.4 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. Technology Inquirer images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 1.0 MB

  • Original 1.5 MB
  • After minification 1.5 MB
  • After compression 521.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 66% of the original size.

CSS Optimization

-84%

Potential reduce by 65.9 kB

  • Original 78.6 kB
  • After minification 68.9 kB
  • After compression 12.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. Technology.inquirer.net needs all CSS files to be minified and compressed as it can save up to 65.9 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 248 (55%)

Requests Now

455

After Optimization

207

The browser has sent 455 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Technology 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 114 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

technology.inquirer.net accessibility score

90

Accessibility Issues

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

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

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

Best Practices

technology.inquirer.net best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

technology.inquirer.net SEO score

85

Search Engine Optimization Advices

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 Technology.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 Technology.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 Technology 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: